Triple
T25942065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westheimer Road |
E653730
|
entity |
| Predicate | hasNotableAreaAlong |
P102115
|
FINISHED |
| Object | Houston Galleria vicinity |
—
|
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: Houston Galleria vicinity | Statement: [Westheimer Road, hasNotableAreaAlong, Houston Galleria vicinity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableAreaAlong Context triple: [Westheimer Road, hasNotableAreaAlong, Houston Galleria vicinity]
-
A.
notableAreaWithin
chosen
Indicates that one area is a particularly significant or noteworthy part located inside another, larger area.
-
B.
hasLandmarkArea
Indicates that a specified area is designated as the landmark area associated with a particular entity or location.
-
C.
hasNotableCollectionArea
Indicates that an entity possesses a significant or distinguished collection focused on a particular subject, theme, or domain.
-
D.
hasAreaName
Indicates that an entity is associated with a specific named geographic or administrative area.
-
E.
hasAreaNumber
Indicates that an entity is associated with a specific area identified by a numerical code.
- 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_69e7ab3fd2f881908837305e4ba98011 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: April 22, 2026, 8:40 a.m.