Triple
T742187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holocene |
E15266
|
entity |
| Predicate | hasBoundaryDefinition |
P3589
|
FINISHED |
| Object | defined by end of Younger Dryas cold event |
—
|
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: defined by end of Younger Dryas cold event | Statement: [Holocene, hasBoundaryDefinition, defined by end of Younger Dryas cold event]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBoundaryDefinition Context triple: [Holocene, hasBoundaryDefinition, defined by end of Younger Dryas cold event]
-
A.
hasBoundaryFeature
Indicates that a boundary (such as an edge, border, or limit) of one entity is characterized, marked, or defined by a specific feature or element.
-
B.
hasBoundaryType
Indicates that one entity has a boundary characterized by a specific type or classification in relation to another entity or context.
-
C.
setsBoundary
Indicates that one entity defines or forms the limiting edge or border of another entity.
-
D.
hasBoundaryEvent
chosen
Indicates that an event occurs at or defines the boundary or limit of another entity or process.
-
E.
borderDefinedBy
Indicates that the boundary or limit of one entity is determined, shaped, or delineated by 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_69a49358aa308190adbc9b5a0a2adcf9 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a60e286c81908787a41cf9b9f150 |
completed | March 1, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69a4a4fdaaf48190985f62acfc069508 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.