Triple
T32965688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhyacian System |
E843360
|
entity |
| Predicate | eonothem |
P175445
|
FINISHED |
| Object | Paleoproterozoic Eonothem |
—
|
NE NERFINISHED |
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: Paleoproterozoic Eonothem | Statement: [Rhyacian System, eonothem, Paleoproterozoic Eonothem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eonothem Context triple: [Rhyacian System, eonothem, Paleoproterozoic Eonothem]
-
A.
eon
Indicates a very long, often immeasurable or indefinitely extended, span of time between entities or events.
-
B.
eve
Indicates a relationship where one entity is the evening or night-time counterpart, phase, or occurrence associated with another entity.
-
C.
oid
Indicates a unique identifier relationship, where the predicate links an entity to its specific object identifier (OID) used to distinguish it from all other entities.
-
D.
nositelé
Indicates that certain entities serve as bearers or carriers of a specified property, role, or characteristic.
-
E.
fromNoseCame
Indicates that something originated from or was expelled out of a nose.
- 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_69f3494af2808190ad98cec2f1bc0fe6 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d1d916f881909575c2b22c416a5b |
completed | May 3, 2026, 4:40 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d0d331dc8190be5aa6bfc6365e67 |
completed | May 3, 2026, 4:36 a.m. |
Created at: May 1, 2026, 1:21 a.m.