Triple
T9625763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erathem |
E232458
|
entity |
| Predicate | symbolizedIn |
P89328
|
FINISHED |
| Object | international chronostratigraphic charts |
—
|
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: international chronostratigraphic charts | Statement: [Erathem, symbolizedIn, international chronostratigraphic charts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolizedIn Context triple: [Erathem, symbolizedIn, international chronostratigraphic charts]
-
A.
symbolizes
Indicates that one entity stands for, represents, or is used as a sign for another entity, concept, or idea.
-
B.
appearsWithSymbol
Indicates that one entity is shown or presented together with a particular symbol in the same visual or contextual setting.
-
C.
symbolLinked
Indicates a relationship where one symbol is connected or associated with another symbol, typically to show reference, correspondence, or linkage between them.
-
D.
emblematicFor
Indicates that something serves as a representative symbol or characteristic example of something else.
-
E.
symbolDescription
Indicates that a symbol is associated with or defined by a particular descriptive explanation or meaning.
- 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_69ca848793ec8190a93a12383a754dc0 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9afb67c88190aa170716f0033752 |
completed | April 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69ccd5acfa5c8190aaba3cf548723604 |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd93fc45c8190a823305e461e581d |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:10 p.m.