Triple
T8416504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ministry of Peace |
E198741
|
entity |
| Predicate | governingBodyInFiction |
P20613
|
FINISHED |
| Object | Party |
—
|
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: Party | Statement: [Ministry of Peace, governingBodyInFiction, Party]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingBodyInFiction Context triple: [Ministry of Peace, governingBodyInFiction, Party]
-
A.
governedByFictional
Indicates that one entity is under the rule, control, or authority of another entity that is fictional or exists only in an imagined context.
-
B.
fictionalEntityType
Indicates that the subject is classified as a particular type or category of fictional entity within a narrative or imaginary context.
-
C.
governingBodyOfType
Indicates that an entity serves as the official governing body for another entity of a specified type or category.
-
D.
governingBodyExample
chosen
Indicates that the subject entity serves as an example or instance of a governing body for the object entity.
-
E.
hasFictionalEstablishmentType
Indicates that an establishment is associated with a particular type or category of fictional setting or institution.
- 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_69ca831201b481909e137936ef99ff11 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb84c5121081908efa3eca25406d3a |
completed | March 31, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69cb70d70ea081909c3dc1bd2ec14f85 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:06 p.m.