Triple
T24044771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arizona–Utah border |
E595486
|
entity |
| Predicate | definedByInstrument |
P154649
|
FINISHED |
| Object | Utah Enabling Act |
—
|
NE NERFINISHED |
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: Utah Enabling Act | Statement: [Arizona–Utah border, definedByInstrument, Utah Enabling Act]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definedByInstrument Context triple: [Arizona–Utah border, definedByInstrument, Utah Enabling Act]
-
A.
formedByInstrument
Indicates that something is created, produced, or brought into existence through the use or action of a specific instrument or tool.
-
B.
definesAsInstrumental
Indicates that one entity is characterized or designated as serving an instrumental or means-to-an-end role in relation to another entity or context.
-
C.
reliesOnInstrument
Indicates that an action or process depends on or is carried out using a particular instrument or tool.
-
D.
designedInstrument
Indicates that an agent is responsible for creating or planning the design of a particular instrument.
-
E.
namedByForInstrument
Indicates that an entity serves as the name or designation assigned specifically for a particular instrument.
- 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_69e288c06a908190899cad4531f32c9a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d8dc8f708190ac6257e65c37bde7 |
completed | April 29, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
| PDg | Predicate description generation | batch_69f1785afe3c81909be28986ffe944bf |
completed | April 29, 2026, 3:17 a.m. |
Created at: April 17, 2026, 10:11 p.m.