Triple
T4339439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pre-1969 Irish Republican Army |
E97542
|
entity |
| Predicate | positionOnBorder |
P45446
|
FINISHED |
| Object | rejection of partition of Ireland |
—
|
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: rejection of partition of Ireland | Statement: [pre-1969 Irish Republican Army, positionOnBorder, rejection of partition of Ireland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnBorder Context triple: [pre-1969 Irish Republican Army, positionOnBorder, rejection of partition of Ireland]
-
A.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
B.
borderPoint
Indicates a point that lies on the boundary between two regions or entities.
-
C.
positionB
Indicates that one entity occupies or is located at a specific position relative to another entity.
-
D.
onBorderBetween
chosen
Indicates that an entity is located along or directly adjacent to the dividing line shared by two distinct regions or areas.
-
E.
operatesOnBorderWith
Indicates that one entity conducts activities or exerts influence along or across the shared border it has with another entity.
- 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_69b3454662a481908fbcd0bbfaa3a0a4 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3516f92588190bdf004d8020c1203 |
completed | March 12, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69b34f4fe1c481908d6d66e15697c04b |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:14 p.m.