Triple
T9900607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ward 5 of Washington, D.C. |
E182270
|
entity |
| Predicate | representativeTitle |
P85416
|
FINISHED |
| Object | Councilmember |
—
|
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: Councilmember | Statement: [Ward 5 of Washington, D.C., representativeTitle, Councilmember]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representativeTitle Context triple: [Ward 5 of Washington, D.C., representativeTitle, Councilmember]
-
A.
hasRepresentativeTitle
Indicates that an entity holds a formal title or designation that serves as its primary or most commonly used label or name.
-
B.
notableOfficerTitle
Indicates that an entity holds or is associated with a particularly distinguished or noteworthy officer position or title.
-
C.
officeHolderTitle
Indicates the official position or title held by a person in an office or role.
-
D.
typicalOfficeHolderTitle
chosen
Indicates the standard or commonly used title typically held by the office holder of a given position or role.
-
E.
electedTitle
Indicates that an entity has been chosen through an election to hold a specific title or office.
- 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_69ca82876f8081909cf75df0f99bb13f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb4e0705c8190bd17e36aff615cdd |
completed | April 2, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69cd1d8c584081908b73de75eb18e438 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:40 p.m.