Triple
T463277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basin and Range Province |
E7387
|
entity |
| Predicate | majorExtensionBegan |
P14293
|
FINISHED |
| Object | 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: Miocene | Statement: [Basin and Range Province, majorExtensionBegan, Miocene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorExtensionBegan Context triple: [Basin and Range Province, majorExtensionBegan, Miocene]
-
A.
mayExtendTo
Indicates that something has the potential or permission to reach, continue, or be applied up to a specified limit, scope, or boundary.
-
B.
extension
Indicates that one entity is a lengthening, continuation, or added part of another entity beyond its original limits.
-
C.
majorVersion
Indicates that one entity specifies or corresponds to the primary (major) version number of another entity in a versioning scheme.
-
D.
missionExtension
Indicates that an existing mission is being prolonged beyond its originally planned duration or scope.
-
E.
extendedBy
Indicates that one entity builds upon, enlarges, or adds to the scope, functionality, or duration of another entity.
- 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_69a2e7e5c5bc8190a1dc8178218fba40 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efc214788190a8dff20fec4412e0 |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2ede8eac081908dffade6a5e7950b |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2ef06d2fc8190b379d575215a8518 |
completed | Feb. 28, 2026, 1:35 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.