Triple
T13750472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Joseph Colton |
E330336
|
entity |
| Predicate | statusInUniverse |
P58920
|
FINISHED |
| Object | legendary figure |
—
|
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: legendary figure | Statement: [General Joseph Colton, statusInUniverse, legendary figure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInUniverse Context triple: [General Joseph Colton, statusInUniverse, legendary figure]
-
A.
inUniverseSocialStatus
Indicates the social rank or standing an entity holds within a specific fictional or defined universe.
-
B.
in-universeStatus
chosen
Indicates the canonical status or role that something holds within the fictional universe or narrative continuity itself.
-
C.
positionInCosmos
Indicates the spatial or hierarchical location of an entity within the broader structure of the cosmos or universe.
-
D.
inUniverse
Indicates that one entity exists, occurs, or is set within the fictional or conceptual universe defined by another entity.
-
E.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
- 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_69d81c573f288190aa2403d484fa3d49 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02148c208190a882927905a861a6 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe950b148190ba0df8a749269ec6 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 10:08 p.m.