Triple
T32094826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Blue Wizards |
E819697
|
entity |
| Predicate | laterConceptualName |
P16968
|
FINISHED |
| Object | Morinehtar |
—
|
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: Morinehtar | Statement: [the Blue Wizards, laterConceptualName, Morinehtar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterConceptualName Context triple: [the Blue Wizards, laterConceptualName, Morinehtar]
-
A.
laterNamed
chosen
Indicates that an entity was given a new name at a later time, linking its original identity to its subsequent name.
-
B.
isConceptualizedAs
Indicates that one entity is mentally represented, interpreted, or understood in terms of another entity.
-
C.
successorConcept
Indicates that one concept directly follows and replaces another in a sequence, versioning, or conceptual progression.
-
D.
conceptualizedFor
Indicates that one entity has been conceived, designed, or mentally framed specifically for use, application, or relevance to another entity.
-
E.
laterTerm
Indicates that one term occurs after another term in a temporal or sequential order.
- 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_69f349004b2481908ce2e50af0d579a8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff7c96e6dc8190b89554480ebcea39 |
completed | May 9, 2026, 6:27 p.m. |
| PD | Predicate disambiguation | batch_69ff7c2381748190ad9a2176e0e478cd |
completed | May 9, 2026, 6:25 p.m. |
Created at: May 1, 2026, 12:25 a.m.