Triple
T35011327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orcs |
E1009945
|
entity |
| Predicate | canonicalName |
P105242
|
FINISHED |
| Object | Orsimer |
—
|
NE NERFINISHED |
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: Orsimer | Statement: [Orcs, canonicalName, Orsimer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canonicalName Context triple: [Orcs, canonicalName, Orsimer]
-
A.
canonicalFor
Indicates that one entity serves as the authoritative or standard representation for another, often consolidating or standing in for its variants or duplicates.
-
B.
commonNameOf
Indicates that one entity is the commonly used or popular name by which the other entity is known.
-
C.
canonicalField
Indicates that one field is the primary or standard representation among a set of related fields, serving as the authoritative or preferred version.
-
D.
canonicallyReferredToAs
chosen
Indicates that one entity is the officially recognized or standard name or label by which another entity is known.
-
E.
canonicalReading
Indicates that one representation of a text or expression is the standard or authoritative version used for reading or interpretation of another.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.