Triple
T33217325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gabilgathol |
E850321
|
entity |
| Predicate | locatedInAge |
P89009
|
FINISHED |
| Object | First Age |
E261178
|
NE 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: First Age | Statement: [Gabilgathol, locatedInAge, First Age]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInAge Context triple: [Gabilgathol, locatedInAge, First Age]
-
A.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
B.
timeLocatedIn
chosen
Indicates that an event, state, or entity occurs, exists, or is valid within a specified time or temporal interval.
-
C.
likelyLocatedIn
Indicates that an entity is probably situated within or associated with a particular location, though not with absolute certainty.
-
D.
takesPlaceInAge
Indicates that an event, process, or state occurs during a particular age or life stage.
-
E.
legalAgingLocation
Indicates the place or jurisdiction in which an entity is legally aged or matures according to applicable laws or regulations.
- F. None of above.
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_69f3496083dc8190b229bb6932dc548b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0379a4086c8190a83df5570f737e15 |
completed | May 12, 2026, 7:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a358137f2b88190beaa17e7dd9954d8 |
completed | June 19, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_6a037049db848190a6268bf1a8a60223 |
completed | May 12, 2026, 6:24 p.m. |
Created at: May 1, 2026, 1:30 a.m.