Triple
T4040105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Highland Village, Texas |
E83925
|
entity |
| Predicate | settledAs |
P53754
|
FINISHED |
| Object | suburban community |
—
|
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: suburban community | Statement: [City of Highland Village, Texas, settledAs, suburban community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settledAs Context triple: [City of Highland Village, Texas, settledAs, suburban community]
-
A.
settled
Indicates that an entity established residence or a stable presence in a place, typically after moving from elsewhere.
-
B.
settlementWith
Indicates a relationship where one party reaches or maintains a settlement or agreement with another party, typically resolving a dispute or claim.
-
C.
settlementState
Indicates the state or status of a settlement process or transaction at a given point in time.
-
D.
hasSettlementAround
Indicates that a settlement is located in the surrounding area of a specified place or feature.
-
E.
associatedWithSettlement
Indicates a relationship where an entity is linked or connected to a particular settlement, such as a town, village, or city.
- F. None of above. chosen
Provenance (4 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_69aed92f7cf0819098e0539bdcc3767f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb39400881909d0f5430f04e441c |
completed | March 9, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69aef900386481909d04555a9ec9b0e3 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aef98ed84c81909dc86097df4afd4f |
completed | March 9, 2026, 4:47 p.m. |
Created at: March 9, 2026, 3:37 p.m.