Triple
T11132099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Houston County, Texas |
E263308
|
entity |
| Predicate | locatedInUSStateRegion |
P49826
|
FINISHED |
| Object | historic and geographic heartland 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: historic and geographic heartland of Texas | Statement: [Houston County, Texas, locatedInUSStateRegion, historic and geographic heartland of Texas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInUSStateRegion Context triple: [Houston County, Texas, locatedInUSStateRegion, historic and geographic heartland of Texas]
-
A.
locatedInStateOrRegion
Indicates that one entity is geographically situated within the boundaries of a specified state or region.
-
B.
locatedInUSRegion
Indicates that one entity is geographically situated within a specified region of the United States.
-
C.
inUSStateRegion
chosen
Indicates that one entity is located within, or belongs to, a specific region of a U.S. state.
-
D.
USStateRegion
Indicates that a U.S. state is located within or belongs to a particular geographic region of the United States.
-
E.
regionOfState
Indicates that one administrative or geographical region is a subdivision or part of a larger 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_69d6aa9c0ba08190bbd19c217489b755 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8347a248190837e8c26f25f553a |
completed | April 9, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69d75ce104908190b6cc31ef2f67846a |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:28 p.m.