Triple
T37664396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elder Guardian |
E937788
|
entity |
| Predicate | spawnsPosition |
P18866
|
FINISHED |
| Object | top of the monument |
—
|
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: top of the monument | Statement: [Elder Guardian, spawnsPosition, top of the monument]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spawnsPosition Context triple: [Elder Guardian, spawnsPosition, top of the monument]
-
A.
spawningLocation
chosen
Indicates the place or environment where an entity originates, appears, or is generated.
-
B.
spawns
Indicates that one entity generates, creates, or gives rise to another entity, often as an origin or source.
-
C.
sporeLocation
Indicates the location or site where spores are present, produced, or deposited in relation to another entity.
-
D.
spawningTrigger
Indicates the condition or event that initiates the creation or appearance of new instances of an entity.
-
E.
spurLocation
Indicates the specific place or region where a spur (such as a projection, offshoot, or secondary feature) is situated relative to another entity.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:18 p.m.