Triple
T20593335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Younger Dryas impact hypothesis |
E505986
|
entity |
| Predicate | boundaryLayer |
P140694
|
FINISHED |
| Object | Younger Dryas boundary |
—
|
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: Younger Dryas boundary | Statement: [Younger Dryas impact hypothesis, boundaryLayer, Younger Dryas boundary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boundaryLayer Context triple: [Younger Dryas impact hypothesis, boundaryLayer, Younger Dryas boundary]
-
A.
boundaryCondition
Indicates the specific constraints or values imposed at the limits or edges of a system, domain, or process that govern its behavior there.
-
B.
boundaryTheory
Indicates that one entity serves as a theoretical or conceptual boundary or limit for another entity within a given framework or domain.
-
C.
hasBoundaryLayerControlSystem
Indicates that an entity is equipped with a system designed to actively manage or manipulate the behavior of its boundary layer flow.
-
D.
boundaryBasis
Indicates that one entity serves as a foundational or defining boundary for another entity.
-
E.
boundaryBetween
Indicates that something serves as a dividing line or limit separating two distinct regions, areas, or entities.
- F. None of above. chosen
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_69e0b4ba6ae88190af871e1f9522c704 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a97d63cc8190853e052d5930470d |
completed | April 20, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_69e59fffe1748190825e4eaa90340631 |
completed | April 20, 2026, 3:39 a.m. |
| PDg | Predicate description generation | batch_69e5a6a9f3f88190b961db9aca36f7da |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:40 a.m.