Triple
T30620568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GCE Ordinary Level |
E779433
|
entity |
| Predicate | phasedOutInCountry |
P123889
|
FINISHED |
| Object | United Kingdom |
—
|
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: United Kingdom | Statement: [GCE Ordinary Level, phasedOutInCountry, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: phasedOutInCountry Context triple: [GCE Ordinary Level, phasedOutInCountry, United Kingdom]
-
A.
abolishedInCountry
chosen
Indicates that something (such as a practice, law, or institution) has been officially ended or eliminated within a specific country.
-
B.
notUsedInCountry
Indicates that a given item, resource, or entity is not utilized, applied, or in operation within a specified country.
-
C.
replacedInCountry
Indicates that one entity has been substituted or superseded by another within the context or jurisdiction of a specific country.
-
D.
discontinuedIn
Indicates that an item, product, or service stopped being produced, offered, or supported starting in a specified time or place.
-
E.
decommissionedBy
Indicates that an entity was formally taken out of service or use by a specific agent or authority.
- 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_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:27 p.m.