Triple
T14197550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bandon (UK Parliament constituency in Parliament of Ireland) |
E351877
|
entity |
| Predicate | representationEnded |
P113175
|
FINISHED |
| Object | 1800 |
—
|
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: 1800 | Statement: [Bandon (UK Parliament constituency in Parliament of Ireland), representationEnded, 1800]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representationEnded Context triple: [Bandon (UK Parliament constituency in Parliament of Ireland), representationEnded, 1800]
-
A.
representationBegins
Indicates that the act or state of representing something starts or comes into effect at a particular point in time.
-
B.
representedByEnd
Indicates that something is represented or characterized by its endpoint or final part.
-
C.
alsoEnded
Indicates that one event or state concluded in addition to another already mentioned event or state.
-
D.
useEnded
Indicates that an entity’s period of using or employing another entity has come to an end.
-
E.
endOf
Indicates that one entity marks the terminating point or final boundary of another entity, event, or interval.
- 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_69d827894ac0819097803e57f3227b23 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61e30f208190b61c1c7bd3501156 |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05baed64819096590e5618a3a8ed |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239a02e881909b0e2679487e4ab2 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 10, 2026, 1:04 a.m.