Triple
T30665169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seville City Council |
E780639
|
entity |
| Predicate | electedEvery |
P118943
|
FINISHED |
| Object | 4 years |
—
|
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: 4 years | Statement: [Seville City Council, electedEvery, 4 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electedEvery Context triple: [Seville City Council, electedEvery, 4 years]
-
A.
isElectedEvery
chosen
Indicates that an entity is chosen for a role or position through an election process at every specified interval or in every relevant instance.
-
B.
electedWithin
Indicates that one entity was chosen or appointed to a position, office, or role within the jurisdiction, boundaries, or organizational scope of another entity.
-
C.
electedAfter
Indicates that one entity was elected to a position at a later time than another entity.
-
D.
electsRepresentativeEvery
Indicates that one entity periodically chooses or votes to select another entity to serve as its representative.
-
E.
isUsuallyElectedFor
Indicates that an entity typically attains a position, role, or office through an election process.
- 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_69f224a6d10481909290be1a00fc83b3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
Created at: April 29, 2026, 8:31 p.m.