Triple
T27724453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Highland Lakes (Texas) |
E699053
|
entity |
| Predicate | passesThroughCounties |
P4247
|
FINISHED |
| Object | Burnet County, Texas |
—
|
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: Burnet County, Texas | Statement: [Highland Lakes (Texas), passesThroughCounties, Burnet County, Texas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passesThroughCounties Context triple: [Highland Lakes (Texas), passesThroughCounties, Burnet County, Texas]
-
A.
passesThroughCounty
chosen
Indicates that a route, path, or boundary traverses or goes through a specified county.
-
B.
passesThroughDistrict
Indicates that something (such as a route, boundary, or path) traverses or goes through a particular district.
-
C.
includesCounty
Indicates that a larger geographic or administrative region contains or encompasses a specific county within its boundaries.
-
D.
passesThroughCountry
Indicates that a route, path, or object traverses or crosses within the boundaries of a specified country.
-
E.
passesThroughAdministrativeRegion
Indicates that a route, path, or movement crosses into or through the territory of a specified administrative 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_69ef591012dc8190a6f1ec994f9f7ff7 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 27, 2026, 3:08 p.m.