Triple
T31821822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mississippian Series |
E812280
|
entity |
| Predicate | systemBelongsTo |
P32380
|
FINISHED |
| Object | Carboniferous System |
—
|
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: Carboniferous System | Statement: [Mississippian Series, systemBelongsTo, Carboniferous System]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: systemBelongsTo Context triple: [Mississippian Series, systemBelongsTo, Carboniferous System]
-
A.
systemUsedBy
Indicates that a particular system is utilized or operated by a specified agent or user.
-
B.
systemEntry
Indicates that an entity is being recorded, registered, or introduced into a particular system or structured environment.
-
C.
associatedSystem
chosen
Indicates that one entity is functionally or contextually linked to a particular system with which it interacts or to which it belongs.
-
D.
systemTypeOperated
Indicates that an entity operates, controls, or runs a particular type of system.
-
E.
systemRefinedBy
Indicates that a system has been improved, optimized, or further developed through the actions, processes, or components specified by the related entity.
- 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_69f348e97fa48190aa06286962af6dee |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 30, 2026, 11:46 p.m.