Triple
T35690979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ison |
E1031290
|
entity |
| Predicate | languageOfCanonStatus |
P25828
|
FINISHED |
| Object | Legends continuity |
—
|
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: Legends continuity | Statement: [Ison, languageOfCanonStatus, Legends continuity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfCanonStatus Context triple: [Ison, languageOfCanonStatus, Legends continuity]
-
A.
storyCanonStatus
Indicates the canonical status of a story relative to an official or primary continuity.
-
B.
hasLanguageStatus
chosen
Indicates that an entity has a particular status or condition regarding its language use, recognition, or classification.
-
C.
franchiseCanonStatus
Indicates whether a work, event, or element is officially recognized as part of the established canon within a franchise.
-
D.
religiousCanonStatus
Indicates the status or standing of something with respect to its recognition or inclusion within a particular religious canon.
-
E.
hasLanguageInUniverse
Indicates that a particular language exists or is used within a specified fictional or conceptual universe.
- 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_69f76e0c73ec819080ab60a9e2f5f1f6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00c9ddd62881909859a36b114a4132 |
completed | May 10, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_6a00c939b88881909d5353db4265e572 |
completed | May 10, 2026, 6:06 p.m. |
Created at: May 3, 2026, 4:05 p.m.