Triple
T3581259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alpha Ridge |
E75802
|
entity |
| Predicate | ageCharacterization |
P2736
|
FINISHED |
| Object | Mesozoic to early Cenozoic |
—
|
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: Mesozoic to early Cenozoic | Statement: [Alpha Ridge, ageCharacterization, Mesozoic to early Cenozoic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageCharacterization Context triple: [Alpha Ridge, ageCharacterization, Mesozoic to early Cenozoic]
-
A.
agePattern
Indicates a relationship where entities share or follow a specific configuration, distribution, or rule regarding their ages.
-
B.
ageProgression
Indicates a temporal relationship where an entity’s age increases or advances over time.
-
C.
ageContext
Indicates the temporal or life-stage context in which an entity’s age is specified or interpreted.
-
D.
ageStatus
Indicates the relationship between an entity and its classification into an age-related category or status (e.g., minor, adult, senior).
-
E.
ageRange
chosen
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
- 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_69ad85d6dc3c8190b491b79b83e25461 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc101738c81908d38987f8fa291ef |
completed | March 8, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69adb83810c481909c645c08b978edc1 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:21 p.m.