Triple
T35461302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montgomery County East County area |
E1024927
|
entity |
| Predicate | postalServiceCityNames |
P154449
|
FINISHED |
| Object | New Caney |
—
|
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: New Caney | Statement: [Montgomery County East County area, postalServiceCityNames, New Caney]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postalServiceCityNames Context triple: [Montgomery County East County area, postalServiceCityNames, New Caney]
-
A.
hasPostalServiceCity
chosen
Indicates that a location is served by or associated with a particular city’s postal service.
-
B.
postalCodeCity
Indicates that a given postal code is associated with, or belongs to, a particular city.
-
C.
postalName
Indicates the standardized name or label used for addressing and postal purposes associated with an entity.
-
D.
postalServiceDesignation
Indicates the official classification or label assigned to an entity by a postal service for mail handling, routing, or addressing purposes.
-
E.
postalService
Indicates a relationship where one entity provides or manages the delivery and handling of mail and packages for another entity.
- 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_69f76dfa20d0819089585dc2cf653aea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.