Triple
T37125082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cathaoirleach |
E919367
|
entity |
| Predicate | hasDeputyTitle |
P3256
|
FINISHED |
| Object | Leas-Chathaoirleach |
—
|
NE NERFINISHED |
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: Leas-Chathaoirleach | Statement: [Cathaoirleach, hasDeputyTitle, Leas-Chathaoirleach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDeputyTitle Context triple: [Cathaoirleach, hasDeputyTitle, Leas-Chathaoirleach]
-
A.
hasDeputyLeaderTitle
chosen
Indicates that an entity holds a specific title associated with the role of deputy leader.
-
B.
mayHaveDeputy
Indicates that an entity is allowed or entitled to have another entity serving as its deputy or subordinate representative.
-
C.
hasDeputyHeads
Indicates that an entity has one or more individuals serving in subordinate leadership roles as deputy heads.
-
D.
deputyOf
Indicates that one entity serves as the subordinate or second-in-command to another, acting with delegated authority on their behalf.
-
E.
wasDeputyIn
Indicates that an entity served in the role of deputy within a specified organization, office, or jurisdiction during a particular period.
- 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_69f76e9d13e48190a108f7fbf80ff375 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff8cecbf048190860b9f72b8753f5c |
completed | May 9, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69ff8c4c39dc8190b5bf35adc1bae7c6 |
completed | May 9, 2026, 7:34 p.m. |
Created at: May 3, 2026, 4:15 p.m.