Triple
T38027616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taurahe |
E948820
|
entity |
| Predicate | relatedLanguageInUniverse |
P164802
|
FINISHED |
| Object | Orcish |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Orcish | Statement: [Taurahe, relatedLanguageInUniverse, Orcish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedLanguageInUniverse Context triple: [Taurahe, relatedLanguageInUniverse, Orcish]
-
A.
hasLanguageInUniverse
Indicates that a particular language exists or is used within a specified fictional or conceptual universe.
-
B.
languageOfFictionalUniverse
Indicates the language used or spoken within a fictional universe or setting.
-
C.
fictionalUniverseLanguage
chosen
Indicates that a language is used or exists within a particular fictional universe.
-
D.
sharesFictionalUniverseWith
Indicates that two entities are set within the same fictional universe or continuity, such that their stories coexist in a shared narrative world.
-
E.
linguisticallyRelatedTo
Indicates that two entities are connected through a linguistic relationship, such as sharing a common language, origin, structure, or other language-based association.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76efd1bc48190a729097fe5177b61 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.