Triple
T2403604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neogene |
E50223
|
entity |
| Predicate | hasLowerBoundaryDefinedBy |
P39203
|
FINISHED |
| Object | base of the Miocene |
—
|
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: base of the Miocene | Statement: [Neogene, hasLowerBoundaryDefinedBy, base of the Miocene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLowerBoundaryDefinedBy Context triple: [Neogene, hasLowerBoundaryDefinedBy, base of the Miocene]
-
A.
hasLower
Indicates that one entity is positioned at a lower level, rank, or value relative to another entity.
-
B.
isUpperBoundFor
Indicates that one value is greater than or equal to every element in a given set or collection, serving as an upper limit for them.
-
C.
lowerLimit
Indicates that one value serves as the minimum or smallest allowable bound or threshold for another value or range.
-
D.
hasMinimumValue
Indicates that an entity possesses a value that is the lowest permissible or observed within a specified set, range, or context.
-
E.
hasBoundaryType
Indicates that one entity has a boundary characterized by a specific type or classification in relation to another entity or context.
- 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_69a88b0339a88190a1207333cd271cc9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abceab9ce881909ae0a2f34515c11e |
completed | March 7, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69abc5a530e8819094105aa92dfaf6b3 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abceaa42b88190a790355100fede3d |
completed | March 7, 2026, 7:07 a.m. |
Created at: March 4, 2026, 7:58 p.m.