Triple
T34000574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas State Highway 249 |
E871803
|
entity |
| Predicate | suburbanSectionLocatedIn |
P15571
|
FINISHED |
| Object | Tomball area |
—
|
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: Tomball area | Statement: [Texas State Highway 249, suburbanSectionLocatedIn, Tomball area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suburbanSectionLocatedIn Context triple: [Texas State Highway 249, suburbanSectionLocatedIn, Tomball area]
-
A.
hasSuburbanSection
chosen
Indicates that a larger route, line, or area includes a portion that passes through or serves a suburban region.
-
B.
isSuburbanNeighborhoodOf
Indicates that one area is a residential neighborhood located within or characteristic of the suburbs of another, typically larger, urban area.
-
C.
locatedInSuburbType
Indicates that one entity is situated within, or belongs to, a specific type or category of suburb associated with the other entity.
-
D.
locatedInNorthernSuburbOf
Indicates that one entity is situated within the northern suburban area relative to another reference location.
-
E.
containsSuburbanAreaOf
Indicates that one geographic region includes within its boundaries a suburban area belonging to or associated with another region.
- 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_69f3499f8cbc81908de6ec89fa91ea8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:50 a.m.