Triple
T26818449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matuyama reversed chron |
E675179
|
entity |
| Predicate | chronCode |
P508
|
FINISHED |
| Object | C2r |
—
|
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: C2r | Statement: [Matuyama reversed chron, chronCode, C2r]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronCode Context triple: [Matuyama reversed chron, chronCode, C2r]
-
A.
raceCode
Indicates the classification of an entity according to a standardized race or ethnicity code.
-
B.
codifiedThrough
Indicates that something is formally established, expressed, or made authoritative by means of a specific codification process, document, or legal/institutional mechanism.
-
C.
numericCode
chosen
Indicates that an entity is associated with a specific numerical identifier or classification code.
-
D.
rankCode
Indicates the specific rank or hierarchical level assigned to an entity, typically encoded as a standardized code.
-
E.
catalogCode
Indicates that an entity is assigned a specific catalog identifier or code used for classification or reference.
- 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_69eee9b6b28481909332f83eb17e5170 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 27, 2026, 4:53 a.m.