Triple
T24070972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lubbock City Council |
E596225
|
entity |
| Predicate | includesTheOffice |
P11900
|
FINISHED |
| Object | Mayor of Lubbock |
—
|
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: Mayor of Lubbock | Statement: [Lubbock City Council, includesTheOffice, Mayor of Lubbock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesTheOffice Context triple: [Lubbock City Council, includesTheOffice, Mayor of Lubbock]
-
A.
includedOffice
chosen
Indicates that one office is contained within, or forms part of, another office or organizational unit.
-
B.
relatesToOffice
Indicates that one entity has a connection, association, or relevance to an office, its functions, or its environment.
-
C.
worksWithOffice
Indicates that an entity collaborates or is professionally associated with a particular office or office-based organization.
-
D.
specifiesOffice
Indicates that an entity is assigned to or associated with a particular office or official position.
-
E.
officeItAbbreviatesMemberOf
Indicates that an office-related abbreviation stands for or is a member of a particular office or organizational unit.
- 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_69e288c3999c8190809b282a04813dec |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1db191d288190af438be742e02252 |
completed | April 29, 2026, 10:19 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:41 p.m.