Triple
T31878009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tertiary System |
E813795
|
entity |
| Predicate | terminologyOf |
P180449
|
FINISHED |
| Object | stratigraphy |
—
|
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: stratigraphy | Statement: [Tertiary System, terminologyOf, stratigraphy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminologyOf Context triple: [Tertiary System, terminologyOf, stratigraphy]
-
A.
languageTerm
Indicates that one entity is a linguistic expression (word, phrase, or term) used to denote or label the other entity.
-
B.
terminologyNote
Indicates that there is an explanatory note or comment clarifying the use, meaning, or nuances of a specific term in the relationship.
-
C.
classificationTerm
Indicates that one entity serves as a categorical label or type used to classify or group another entity.
-
D.
officialTerminology
Indicates that the associated term is the formally recognized or standard expression used in an official or authoritative context for a given concept or entity.
-
E.
keyTerm
Indicates that a term functions as a primary or central concept within a given context or information structure.
- 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_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
| PDg | Predicate description generation | batch_69f74061c440819080434155c2d60341 |
completed | May 3, 2026, 12:32 p.m. |
Created at: April 30, 2026, 11:55 p.m.