Triple
T1898346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Ordnance |
E37632
|
entity |
| Predicate | privatizationStatus |
P7658
|
FINISHED |
| Object | privatized |
—
|
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: privatized | Statement: [Royal Ordnance, privatizationStatus, privatized]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: privatizationStatus Context triple: [Royal Ordnance, privatizationStatus, privatized]
-
A.
privatizedOn
Indicates the date or point in time when an entity transitioned from public or state ownership/control to private ownership/control.
-
B.
publicSectorStatus
chosen
Indicates whether an entity is part of, controlled by, or associated with the public sector (e.g., government or state-owned institutions).
-
C.
autonomyStatus
Indicates the degree to which an entity operates independently or with self-governed control, without external direction or intervention.
-
D.
governingStatus
Indicates the political or administrative condition under which an entity is currently governed or exercising governing authority.
-
E.
federalStatus
Indicates that an entity holds a particular legal or administrative status under federal (national) authority or jurisdiction.
- 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_69a8861be7148190a680937ec451a304 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb170657481908662089511a8f301 |
completed | March 7, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69abafe7e7e88190b58c0df59187c0c2 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.