Triple
T27214557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom |
E684100
|
entity |
| Predicate | primaryAdversaryGroupType |
P58016
|
FINISHED |
| Object | secret organization |
—
|
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: secret organization | Statement: [Kingdom, primaryAdversaryGroupType, secret organization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAdversaryGroupType Context triple: [Kingdom, primaryAdversaryGroupType, secret organization]
-
A.
primaryAdversaryContext
Indicates the main opposing force or conflict-driving element that defines the central adversarial situation within a given context.
-
B.
primaryAntagonistType
chosen
Indicates the role or category of the main opposing force or adversary that serves as the central source of conflict.
-
C.
hasAntagonistGroup
Indicates that an entity is opposed or challenged by a specific group acting as its antagonist.
-
D.
primaryAdversaryImplied
Indicates that an entity is understood or suggested, rather than explicitly stated, to be the main opponent or chief adversary of another entity.
-
E.
opposedGroupType
Indicates that one group is characterized as being in opposition to another group based on its type or classification.
- 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_69eefad339a08190aeacb2a198f1a39b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69ff1e3e13c08190bb8990c44716b746 |
completed | May 9, 2026, 11:45 a.m. |
| PD | Predicate disambiguation | batch_69ff1dfcaf2c8190aaf2b428d57b7782 |
completed | May 9, 2026, 11:43 a.m. |
Created at: April 27, 2026, 9:40 a.m.