Triple
T28904804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miniplenty |
E733042
|
entity |
| Predicate | newspeakAbbreviationOf |
P36183
|
FINISHED |
| Object | Ministry of Plenty |
—
|
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: Ministry of Plenty | Statement: [Miniplenty, newspeakAbbreviationOf, Ministry of Plenty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: newspeakAbbreviationOf Context triple: [Miniplenty, newspeakAbbreviationOf, Ministry of Plenty]
-
A.
abbreviationUsedFor
chosen
Indicates that a particular shortened form or acronym is used to represent or stand in for a longer term, name, or expression.
-
B.
abbreviationUsedBy
Indicates that a particular abbreviation is employed or adopted by a specified entity in its communication, documentation, or usage.
-
C.
abbreviation
Indicates that one term is a shortened or contracted form that stands for another, longer expression.
-
D.
abbreviationOrShortForm
Indicates that one term is an abbreviation or shortened form of another term.
-
E.
abbreviationCoined
Indicates that a specific abbreviation was first created, introduced, or established in association with a particular term, phrase, or context.
- 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_69f05b096d208190958a57d2e4b5a93a |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65ada0060819098ff14053a958b64 |
completed | May 2, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69f6576487e081908d802f1caf59c423 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 8:06 a.m.