Triple
T24672347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bowie County, Texas |
E610874
|
entity |
| Predicate | isLocatedInCornerOfState |
P96807
|
FINISHED |
| Object | northeastern corner of Texas |
—
|
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: northeastern corner of Texas | Statement: [Bowie County, Texas, isLocatedInCornerOfState, northeastern corner of Texas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedInCornerOfState Context triple: [Bowie County, Texas, isLocatedInCornerOfState, northeastern corner of Texas]
-
A.
hasCapitalOfContainingState
Indicates that a capital city is the official capital of a state that geographically contains a given area or entity.
-
B.
stateGovernorResidenceLocatedIn
Indicates that the official residence of a state governor is located within a specified geographic or political area.
-
C.
hasStateOrDistrict
Indicates that an entity is associated with, located in, or belongs to a particular state or district.
-
D.
locatedInStateOrRegion
chosen
Indicates that one entity is geographically situated within the boundaries of a specified state or region.
-
E.
housedInState
Indicates that an entity is located or situated within the boundaries of a particular state.
- 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_69e2c4d505cc8190981881df06c0bf52 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 2:47 a.m.