Triple
T4145542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avalonia microcontinent |
E89372
|
entity |
| Predicate | riftEventAgeApproximate |
P51855
|
FINISHED |
| Object | around 600–550 million years ago |
—
|
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: around 600–550 million years ago | Statement: [Avalonia microcontinent, riftEventAgeApproximate, around 600–550 million years ago]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riftEventAgeApproximate Context triple: [Avalonia microcontinent, riftEventAgeApproximate, around 600–550 million years ago]
-
A.
containsAge
chosen
Indicates that one entity includes or specifies the age value or age-related information of another entity.
-
B.
hasRelativeAge
Indicates that one entity has an age that is defined or compared in relation to the age of another entity.
-
C.
youngestEvent
Indicates that the referenced event is the most recent or last-occurring event among a set of events.
-
D.
ageAtParty
Indicates the age a person (or entity) has at the time a particular party or event takes place.
-
E.
ageStatus
Indicates the relationship between an entity and its classification into an age-related category or status (e.g., minor, adult, senior).
- 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_69aed95785788190ae75bcf0cd1cafdf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af033ef6648190adde17f943d89c78 |
completed | March 9, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69af018c101081909070da5b11e5eb3d |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:43 p.m.