Triple
T32440356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queens Chapel |
E828995
|
entity |
| Predicate | wardRepresentative |
P174089
|
FINISHED |
| Object | Ward 5 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: Ward 5 Councilmember | Statement: [Queens Chapel, wardRepresentative, Ward 5 Councilmember]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wardRepresentative Context triple: [Queens Chapel, wardRepresentative, Ward 5 Councilmember]
-
A.
countyRepresented
Indicates that a person or representative serves as the official representative for a particular county in a governing or organizational context.
-
B.
representativeDetermined
Indicates that an official representative has been identified and designated for a particular entity or context.
-
C.
livingRepresentatives
Indicates that certain entities serve as currently living representatives or embodiments of other entities.
-
D.
eraRepresented
Indicates that a subject depicts, symbolizes, or stands for a particular historical or temporal era.
-
E.
earlyRepresentative
Indicates that one entity serves as an initial or pioneering representative or example of another entity in time or development.
- 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_69f3491bf298819097b610f772d54a6d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2e2652881909198964213886476 |
completed | May 3, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bb344bb48190a8089f29c0063ded |
completed | May 3, 2026, 3:04 a.m. |
Created at: May 1, 2026, 12:55 a.m.