Triple
T20670925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premier Peer of Ireland |
E508019
|
entity |
| Predicate | governsPrecedenceAmong |
P1616
|
FINISHED |
| Object | Irish peers |
—
|
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: Irish peers | Statement: [Premier Peer of Ireland, governsPrecedenceAmong, Irish peers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsPrecedenceAmong Context triple: [Premier Peer of Ireland, governsPrecedenceAmong, Irish peers]
-
A.
confersPrecedenceIn
chosen
Indicates that one entity is granted higher priority, rank, or standing over another within a specified context or domain.
-
B.
orderPrecedence
Indicates that one entity must come before another in a defined sequence or priority order.
-
C.
bindingPrecedent
Indicates that a prior decision or ruling must be followed as an authoritative legal standard in deciding a current case.
-
D.
hasPrecedence
Indicates that one entity occurs, is considered, or is applied before another in order, priority, or importance.
-
E.
precedentFor
Indicates that one situation, decision, or case serves as an authoritative example or basis for deciding or interpreting another.
- 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_69e0b4c059bc81908ea762cd73ea4424 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b5c92aa8819096fbe0ca5101d01b |
completed | April 20, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69e5c03caee881908be4dd25796a03d5 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:44 a.m.