Triple
T25037880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harker Heights City Hall |
E627028
|
entity |
| Predicate | governingBodyMeetingPlace |
P143433
|
FINISHED |
| Object | Harker Heights City Council |
—
|
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: Harker Heights City Council | Statement: [Harker Heights City Hall, governingBodyMeetingPlace, Harker Heights City Council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingBodyMeetingPlace Context triple: [Harker Heights City Hall, governingBodyMeetingPlace, Harker Heights City Council]
-
A.
locationOfGoverningBody
Indicates the place where a governing body is based or carries out its official functions.
-
B.
capitalOfMeetingPlace
Indicates that a location serves as the capital city where a particular meeting or set of meetings takes place.
-
C.
governingBodyMetHere
chosen
Indicates that a governing body held a meeting or conducted official proceedings at this location.
-
D.
governingConferenceHeadquarters
Indicates that the headquarters of a governing conference is located at a particular place or facility.
-
E.
locationOfCabinetMeetings
Indicates the place where cabinet meetings are held.
- 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_69e2ff2a2c088190be513727ee8bfe78 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 18, 2026, 6:08 a.m.