Triple
T28904629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | government of Oceania |
E733038
|
entity |
| Predicate | controlsClass |
P187573
|
FINISHED |
| Object | Outer Party |
—
|
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: Outer Party | Statement: [government of Oceania, controlsClass, Outer Party]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlsClass Context triple: [government of Oceania, controlsClass, Outer Party]
-
A.
designClass
Indicates that one entity is the design or blueprint class from which the other entity is derived or instantiated.
-
B.
clase
Indicates a classification or type relationship, where one entity is categorized as belonging to a particular class or category defined by another entity.
-
C.
settingClass
Indicates that something belongs to, is categorized under, or is associated with a particular class or type used as its setting or context.
-
D.
structureClass
Indicates a classification relationship where an entity is assigned to or associated with a particular structural type or category.
-
E.
navigationClass
Indicates that one entity serves as a navigation or menu grouping that organizes or links to another entity within a navigational structure.
- F. None of above. chosen
Provenance (4 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_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb6fdab95c81909acff3c6a2359787 |
completed | May 6, 2026, 4:44 p.m. |
Created at: April 28, 2026, 8:06 a.m.