Triple
T7581485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Last Glacial Maximum |
E179498
|
entity |
| Predicate | hasKeyProxy |
P14117
|
FINISHED |
| Object | oxygen isotope ratios |
—
|
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: oxygen isotope ratios | Statement: [Last Glacial Maximum, hasKeyProxy, oxygen isotope ratios]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyProxy Context triple: [Last Glacial Maximum, hasKeyProxy, oxygen isotope ratios]
-
A.
hasKeyElement
Indicates that one entity contains or depends on another entity that serves as a primary or essential component.
-
B.
hasKeyFunction
Indicates that one entity serves as a primary or essential function or role for another entity.
-
C.
hasKeyPass
Indicates that an entity possesses or is granted a key-based pass that allows access or authorization to something.
-
D.
hasKeyAspect
chosen
Indicates that something possesses a central, defining, or particularly important feature or characteristic.
-
E.
hasKeyDemand
Indicates that one entity requires or insists on another entity as a crucial or primary condition, resource, or requirement.
- 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_69c69f327db881909a21ae3b156f8ded |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f97717048190b0ca1a74ed8a817e |
completed | March 27, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e04c2c8190a889d928515d9b8e |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:52 p.m.