Triple
T35687476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Amity government |
E1031188
|
entity |
| Predicate | governingBodySeatsFilledBy |
P203752
|
FINISHED |
| Object | elected officials |
—
|
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: elected officials | Statement: [City of Amity government, governingBodySeatsFilledBy, elected officials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingBodySeatsFilledBy Context triple: [City of Amity government, governingBodySeatsFilledBy, elected officials]
-
A.
governingBodySeats
Indicates the number of seats or positions an entity holds in a specified governing body.
-
B.
parliamentarySeatCount
Indicates the number of seats a party, group, or entity holds in a parliamentary body.
-
C.
legislativeAssemblySeats
Indicates the number of seats an entity holds or is allocated in a legislative assembly.
-
D.
numberOfElectedMembers
Indicates the total count of individuals who have been formally chosen through an election to serve as members of a given body or group.
-
E.
parliamentarySeatsTotal
Indicates the total number of seats in a given parliament or parliamentary body.
- 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_69f76e0bb6608190ad3a1880be54a17d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a01e3a2d0e08190a7d5622920dc56e6 |
completed | May 11, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_6a01e3013e7881909f0cdca25a53c009 |
completed | May 11, 2026, 2:09 p.m. |
| PDg | Predicate description generation | batch_6a01e3a226948190b9c0e693a6a5e4c1 |
completed | May 11, 2026, 2:11 p.m. |
Created at: May 3, 2026, 4:05 p.m.