Triple
T25176679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lodgepole Formation |
E630465
|
entity |
| Predicate | ageQualifier |
P146103
|
FINISHED |
| Object | early Mississippian |
—
|
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: early Mississippian | Statement: [Lodgepole Formation, ageQualifier, early Mississippian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageQualifier Context triple: [Lodgepole Formation, ageQualifier, early Mississippian]
-
A.
ageStatus
Indicates the relationship between an entity and its classification into an age-related category or status (e.g., minor, adult, senior).
-
B.
ageType
chosen
Indicates the specific categorization or classification of an age value (e.g., actual, estimated, range-based) associated with an entity.
-
C.
containsAge
Indicates that one entity includes or specifies the age value or age-related information of another entity.
-
D.
ageBased
Indicates a relationship or condition that depends on or is determined by the age of the entities involved.
-
E.
ageStatement
Indicates that a statement expresses or asserts the age of an entity in terms of time lived or existed.
- 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_69e75a88fdf081908e47ae6e195c14e1 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46dc040088190958bb7a6633fd016 |
completed | May 1, 2026, 9:09 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 12:34 p.m.