Triple
T30750428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rangeomorphs |
E782940
|
entity |
| Predicate | associatedEon |
P97345
|
FINISHED |
| Object | Neoproterozoic Eon |
E45475
|
NE 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: Neoproterozoic Eon | Statement: [Rangeomorphs, associatedEon, Neoproterozoic Eon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedEon Context triple: [Rangeomorphs, associatedEon, Neoproterozoic Eon]
-
A.
belongsToEon
chosen
Indicates that something is a member or part of a specific eon in a temporal or classificatory hierarchy.
-
B.
associatedBeings
Indicates that two or more beings are linked or connected to each other in some relevant way.
-
C.
associatedUniverse
Indicates that one entity is linked or belongs to a particular universe, realm, or overarching world context.
-
D.
associatedThrough
Indicates that two entities are connected or related to each other by means of a specified intermediary, context, or linkage.
-
E.
associatedEnsembleOf
Indicates that one entity is linked or connected to a particular ensemble, typically as a member, contributor, or related component of that group.
- F. None of above.
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_69f224af8d8481908bea03890c5618be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2a1e0b73d88190a6e80588bb4ba543 |
completed | June 11, 2026, 2:31 a.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:38 p.m.