Triple
T4145543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avalonia microcontinent |
E89372
|
entity |
| Predicate | collisionEventAgeApproximate |
P54601
|
FINISHED |
| Object | around 430–400 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 430–400 million years ago | Statement: [Avalonia microcontinent, collisionEventAgeApproximate, around 430–400 million years ago]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collisionEventAgeApproximate Context triple: [Avalonia microcontinent, collisionEventAgeApproximate, around 430–400 million years ago]
-
A.
collisionType
Indicates the specific kind or category of collision that occurs between two or more entities.
-
B.
victimAge
Indicates the age of the person who is the victim in the described event or situation.
-
C.
containsAge
Indicates that one entity includes or specifies the age value or age-related information of another entity.
-
D.
collisionDomain
Indicates that two or more network entities share the same collision domain, meaning their transmissions can interfere and cause packet collisions with each other.
-
E.
damageYear
Indicates the year in which the damage to an entity occurred or was recorded.
- 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_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. |
| PDg | Predicate description generation | batch_69af033d94888190b34349e355b874ef |
completed | March 9, 2026, 5:28 p.m. |
Created at: March 9, 2026, 3:43 p.m.