Triple
T28896578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ecco: The Tides of Time |
E732848
|
entity |
| Predicate | notableLevelType |
P203580
|
FINISHED |
| Object | 3D tunnel stages |
—
|
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: 3D tunnel stages | Statement: [Ecco: The Tides of Time, notableLevelType, 3D tunnel stages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLevelType Context triple: [Ecco: The Tides of Time, notableLevelType, 3D tunnel stages]
-
A.
notableLevel
Indicates the degree or extent to which something is considered notable or significant.
-
B.
notableRank
Indicates that an entity holds a distinguished or significant position or level within a ranking or hierarchy.
-
C.
notableHierarchy
Indicates that one entity holds a higher or more prominent rank, status, or level of importance relative to another within an ordered structure or system.
-
D.
notableOfficeLevel
Indicates that an entity holds or is associated with a notable office or position at a specified hierarchical level.
-
E.
notableTypeOf
Indicates that one entity is a particularly prominent, well-known, or exemplary instance or subtype of another entity.
- F. None of above. chosen
Provenance (4 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_6a01a9e333fc819087d583ff319be0b3 |
completed | May 11, 2026, 10:05 a.m. |
| PD | Predicate disambiguation | batch_6a01a877c9e08190b0678618d3533286 |
completed | May 11, 2026, 9:59 a.m. |
| PDg | Predicate description generation | batch_6a01a9e27adc81908b90db24e93f3be0 |
completed | May 11, 2026, 10:05 a.m. |
Created at: April 28, 2026, 7:59 a.m.