Triple
T26818073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Last Glacial Period |
E675171
|
entity |
| Predicate | endCoincidesWith |
P4881
|
FINISHED |
| Object | beginning of Holocene |
—
|
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: beginning of Holocene | Statement: [Last Glacial Period, endCoincidesWith, beginning of Holocene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endCoincidesWith Context triple: [Last Glacial Period, endCoincidesWith, beginning of Holocene]
-
A.
coincidesWith
chosen
Indicates that two entities occupy the same position, time, or state such that they exactly overlap or occur together.
-
B.
endsOn
Indicates that one entity terminates or concludes precisely at the boundary or endpoint of another entity.
-
C.
overlapsWith
Indicates that two entities share a common part or region in space, time, or extent, but neither is completely contained within the other.
-
D.
endsInKey
Indicates that an event, sequence, or musical piece concludes in a specified key.
-
E.
notCoterminousWith
Indicates that two entities do not share the same boundaries in space, time, or extent and therefore are not exactly coincident.
- 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_69eee9b6b28481909332f83eb17e5170 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61a87b34081909f7e7276e9e9c82b |
completed | May 2, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 4:53 a.m.