Triple
T30620593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GCE Ordinary Level |
E779433
|
entity |
| Predicate | replacedInNorthernIrelandBy |
P96733
|
FINISHED |
| Object | GCSE |
—
|
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: GCSE | Statement: [GCE Ordinary Level, replacedInNorthernIrelandBy, GCSE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedInNorthernIrelandBy Context triple: [GCE Ordinary Level, replacedInNorthernIrelandBy, GCSE]
-
A.
replacedByInNorthernIreland
chosen
Indicates that one entity has been superseded or taken over by another specifically within the jurisdiction of Northern Ireland.
-
B.
replacedInWalesBy
Indicates that something previously in use or effect in Wales has been superseded or substituted by another specific thing.
-
C.
replacesInScotland
Indicates that one entity takes over the role, function, or position of another entity specifically within the context of Scotland.
-
D.
replacedByInEurope
Indicates that one entity has been superseded or substituted by another specifically within the geographic context of Europe.
-
E.
hasCountyInNorthernIreland
Indicates that a place or administrative area is located within a county that is part of Northern Ireland.
- 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_69f224a3307081909a6dca8ca75dbf48 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: April 29, 2026, 8:27 p.m.