Triple
T8123077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cumann na nGaedheal |
E189654
|
entity |
| Predicate | inGovernmentUntil |
P31613
|
FINISHED |
| Object | 1932 |
—
|
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: 1932 | Statement: [Cumann na nGaedheal, inGovernmentUntil, 1932]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inGovernmentUntil Context triple: [Cumann na nGaedheal, inGovernmentUntil, 1932]
-
A.
hasBeenInGovernmentUntil
chosen
Indicates that an entity held a government position continuously up to a specified end time or date.
-
B.
servedInGovernmentWith
Indicates that two individuals held positions in the same government or administration during an overlapping period of time.
-
C.
endOfGovernmentTerm
Indicates that a specific point in time marks the conclusion of a particular government's or officeholder's official term in power.
-
D.
enteredGovernment
Indicates that an entity assumed a role or position within a governmental body or institution.
-
E.
usedInGovernmentBody
Indicates that an entity is employed by, serves within, or is otherwise functionally involved in the operations of a government 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_69ca82bb74848190afb1f18640632c10 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4664fef881908b0dc7b158aca398 |
completed | March 31, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69cb368e7f4c81909aabd7716f0de79d |
completed | March 31, 2026, 2:50 a.m. |
Created at: March 30, 2026, 5:33 p.m.