Triple
T7690708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mayo (Dáil constituency) |
E174236
|
entity |
| Predicate | previousNumberOfRepresentatives |
P4273
|
FINISHED |
| Object | 4 |
—
|
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 | Statement: [Mayo (Dáil constituency), previousNumberOfRepresentatives, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousNumberOfRepresentatives Context triple: [Mayo (Dáil constituency), previousNumberOfRepresentatives, 4]
-
A.
numberOfRepresentatives
chosen
Indicates the quantity of representatives associated with a given entity or unit.
-
B.
previousNumberOfConstituents
Indicates the number of constituents an entity had at an earlier point in time, before its current state.
-
C.
numberOfColoniesRepresented
Indicates the count of distinct colonies that are represented or involved in relation to a given entity or context.
-
D.
previousCongress
Indicates that one legislative body or session directly precedes another in chronological order.
-
E.
electRepresentativesTo
Indicates the action by which a group or body chooses individuals to serve as its official representatives in another governing or decision-making body.
- 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_69c6995966348190939e6c37ba272c06 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c706d1f0208190bc5b695aa5736244 |
completed | March 27, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69c70163dea88190ae729df50e63dfd7 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:02 p.m.