Triple
T29744838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quynh Mai Ward |
E752719
|
entity |
| Predicate | locatedInDistrictType |
P176124
|
FINISHED |
| Object | urban district |
—
|
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: urban district | Statement: [Quynh Mai Ward, locatedInDistrictType, urban district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInDistrictType Context triple: [Quynh Mai Ward, locatedInDistrictType, urban district]
-
A.
basedInDistrict
Indicates that an entity is located or has its primary base of operations within a specific administrative district.
-
B.
occursInDistrict
Indicates that an event or activity takes place within the boundaries of a specific district.
-
C.
locatedInRegionalDistrict
Indicates that one entity is geographically situated within the boundaries of a specified regional district.
-
D.
withinDistrictType
chosen
Indicates that one entity is located inside or falls under the jurisdiction of a specific type or category of district.
-
E.
locatedNearDistrict
Indicates that one entity is situated in close geographic proximity to a particular district.
- 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_69f0d62b064081908c1ae61cd68fb139 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a005247dba08190acadf962bcefe4a0 |
completed | May 10, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_6a00519029848190a234358dfba45084 |
completed | May 10, 2026, 9:36 a.m. |
Created at: April 28, 2026, 7:50 p.m.