Triple
T2657846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rio Bravo |
E54656
|
entity |
| Predicate | setInEnvironment |
P13408
|
FINISHED |
| Object | frontier town |
—
|
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: frontier town | Statement: [Rio Bravo, setInEnvironment, frontier town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setInEnvironment Context triple: [Rio Bravo, setInEnvironment, frontier town]
-
A.
usedInEnvironment
chosen
Indicates that something is utilized or operates within a particular environment or context.
-
B.
setInState
Indicates that an entity is located within, or belongs to, a particular state or state-level jurisdiction.
-
C.
setInEvent
Indicates that an entity is situated within, occurs during, or is contextually located in a particular event.
-
D.
setInUniverse
Indicates that something is located within, belongs to, or takes place in a particular fictional or conceptual universe.
-
E.
supportsEnvironment
Indicates that one entity provides the necessary conditions, compatibility, or resources for another entity to operate or exist within a particular environment.
- 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_69ab49e028948190b97e01d73548b1d9 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd94c61a08190bdf5e1caeff3e788 |
completed | March 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69abd81768748190bd965f367cf6ef37 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.