Triple
T15282634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2023 Dallas City Council election |
E365308
|
entity |
| Predicate | positionStartAfterElection |
P97637
|
FINISHED |
| Object | 2023 |
—
|
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: 2023 | Statement: [2023 Dallas City Council election, positionStartAfterElection, 2023]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionStartAfterElection Context triple: [2023 Dallas City Council election, positionStartAfterElection, 2023]
-
A.
electedAfter
Indicates that one entity was elected to a position at a later time than another entity.
-
B.
positionBeforeElection
chosen
Indicates that an entity held a particular position or office prior to a specified election.
-
C.
formedAfterElection
Indicates that an entity (such as a government, cabinet, or committee) was established or came into existence following the conclusion of an election.
-
D.
providedForElectionOf
Indicates that one entity supplied resources, support, or services specifically to facilitate or influence the election of another entity.
-
E.
predecessorElection
Indicates that one election immediately preceded another in a temporal or sequential order.
- 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_69d85a103d9081908c1ea6c4c73ac8e3 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00e51f82081909f63d14b589d5587 |
completed | April 15, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69deca90739081909bd1b797cdb8af2b |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:15 a.m.