Triple
T13747254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teton fault |
E330244
|
entity |
| Predicate | formsFrontOf |
P63831
|
FINISHED |
| Object | eastern front of the Teton Range |
—
|
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: eastern front of the Teton Range | Statement: [Teton fault, formsFrontOf, eastern front of the Teton Range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsFrontOf Context triple: [Teton fault, formsFrontOf, eastern front of the Teton Range]
-
A.
frontType
Indicates the type or category of a front (e.g., boundary or leading side) that one entity presents or forms relative to another.
-
B.
frontOf
chosen
Indicates that one entity is positioned directly before another along a primary viewing or movement direction.
-
C.
formsPreambleOf
Indicates that one element serves as the introductory or preface section to another, typically larger, document or text.
-
D.
frontDesign
Indicates that one entity serves as the primary or visible front-facing design or appearance of another entity.
-
E.
formsTopOf
Indicates that one entity constitutes the uppermost part or surface of another entity.
- 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_69d81c573f288190aa2403d484fa3d49 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02132a108190aca728b95e83af01 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe950b148190ba0df8a749269ec6 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 10:08 p.m.