Triple
T31138787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BT postcode area |
E793723
|
entity |
| Predicate | coversMajorityOf |
P181258
|
FINISHED |
| Object | Northern Ireland |
—
|
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: Northern Ireland | Statement: [BT postcode area, coversMajorityOf, Northern Ireland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversMajorityOf Context triple: [BT postcode area, coversMajorityOf, Northern Ireland]
-
A.
hasMajorityOf
Indicates that one entity possesses or controls more than half of the total quantity, members, or share of another entity.
-
B.
hasMajority
Indicates that one entity holds more than half of the total share, control, or quantity in relation to another entity or set.
-
C.
hasMajorityIn
Indicates that one entity holds more than half of the control, ownership, or representation within another entity or group.
-
D.
replacesMajorityOf
Indicates that one entity takes over and substitutes for most of the function, role, or components previously fulfilled by another entity.
-
E.
votedWithMajorityIn
Indicates that an entity cast its vote in alignment with the majority decision within a given voting event or body.
- F. None of above. chosen
Provenance (4 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f76759b3c48190ad8f1b33596f98c4 |
completed | May 3, 2026, 3:18 p.m. |
Created at: April 29, 2026, 9:05 p.m.