Triple
T24011987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dodge City Hall |
E594554
|
entity |
| Predicate | meetingFacility |
P50741
|
FINISHED |
| Object | city council chamber |
—
|
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: city council chamber | Statement: [Dodge City Hall, meetingFacility, city council chamber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meetingFacility Context triple: [Dodge City Hall, meetingFacility, city council chamber]
-
A.
meetingPlaceOf
chosen
Indicates the location where a particular meeting or gathering takes place or is held for the referenced entities.
-
B.
meetingType
Indicates the specific category or format of a meeting that characterizes how it is organized or conducted.
-
C.
meeting
Indicates that two or more entities come together at the same time and place for discussion, decision-making, or coordinated activity.
-
D.
meetingContext
Indicates the situational setting, circumstances, or background conditions in which a meeting takes place.
-
E.
hasConferenceSpace
Indicates that an entity provides or includes dedicated space suitable for holding conferences, meetings, or similar gatherings.
- 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_69e288bc8f608190ac4af29f0bd1c744 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d59d6a2c8190860a44c056030826 |
completed | April 29, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:41 p.m.