Triple
T2047024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neoproterozoic Era |
E45475
|
entity |
| Predicate | locationOf |
P40
|
FINISHED |
| Object | glacial deposits on multiple continents |
—
|
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: glacial deposits on multiple continents | Statement: [Neoproterozoic Era, locationOf, glacial deposits on multiple continents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOf Context triple: [Neoproterozoic Era, locationOf, glacial deposits on multiple continents]
-
A.
locatedIn
chosen
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
B.
propertyLocation
Indicates the geographical place or address where a property is situated or found.
-
C.
locationOfFacility
Indicates that a facility is situated at or associated with a specific geographic location.
-
D.
possibleLocation
Indicates that an entity may be located at, or could plausibly occur in, a specified place or spatial context.
-
E.
locationInSystem
Indicates that one entity is situated within or belongs to the spatial or organizational bounds of a particular system.
- 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_69a8891948208190ab7898da21824c77 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abbc2c3f6c8190aff07097b2654e52 |
completed | March 7, 2026, 5:48 a.m. |
| PD | Predicate disambiguation | batch_69abb7aa00d4819086d347d9a08f81a0 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:39 p.m.