Triple
T13462765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Real County, Texas |
E311412
|
entity |
| Predicate | hasCommunity |
P2605
|
FINISHED |
| Object | Leakey, Texas |
E1218559
|
NE 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: Leakey, Texas | Statement: [Real County, Texas, hasCommunity, Leakey, Texas]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Leakey, Texas Context triple: [Real County, Texas, hasCommunity, Leakey, Texas]
-
A.
Leakey, Texas
chosen
Leakey, Texas is a small town in the Texas Hill Country known as a gateway to outdoor recreation along the Frio River.
-
B.
Leo, Texas
Leo, Texas is a small rural unincorporated community located in Cooke County in north-central Texas.
-
C.
Leonard, Texas
Leonard, Texas is a small rural city in North Texas known for its tight-knit community and annual Leonard Picnic celebration.
-
D.
Lockhart, Texas
Lockhart, Texas is a small Central Texas city renowned as the "Barbecue Capital of Texas" and a historic hub of the Austin–San Antonio region.
-
E.
Millican, Texas
Millican, Texas is a small rural community in east-central Texas known for its historic role as an early railroad town.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf0d95fc81909d9f73d5315dc7b4 |
completed | April 12, 2026, 2:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a006ec7a4748190822e66a756bc95b9 |
completed | May 10, 2026, 11:40 a.m. |
Created at: April 9, 2026, 9:41 p.m.