Triple
T14865990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District XIV |
E349616
|
entity |
| Predicate | hasRelativePositionToDistrictXIII |
P115935
|
FINISHED |
| Object | adjacent |
—
|
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: adjacent | Statement: [District XIV, hasRelativePositionToDistrictXIII, adjacent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelativePositionToDistrictXIII Context triple: [District XIV, hasRelativePositionToDistrictXIII, adjacent]
-
A.
basedInDistrict
Indicates that an entity is located or has its primary base of operations within a specific administrative district.
-
B.
hasNearbyPrecinct
Indicates that one location has a police precinct or similar administrative station situated close to it in geographic proximity.
-
C.
meetsInDistrict
Indicates that two or more entities hold a meeting within the boundaries of a specified administrative district.
-
D.
hasCouncilDistrict
Indicates that an entity is located within or represented by a specific council district.
-
E.
hasDistrictOfficeLocation
Indicates that an entity’s district office is located at a specified place or address.
- 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_69d822ed7e1881909b90fca143ad7e34 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded5761c688190b4477cb081554b51 |
completed | April 15, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69de8c1798c08190b433e9ad21e41a42 |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4b67cc8190b84b59fcec5cf579 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:55 a.m.