Triple
T29862976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | guerrilla diplomacy |
E758373
|
entity |
| Predicate | typicalActors |
P204005
|
FINISHED |
| Object | non-state actors |
—
|
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: non-state actors | Statement: [guerrilla diplomacy, typicalActors, non-state actors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalActors Context triple: [guerrilla diplomacy, typicalActors, non-state actors]
-
A.
usedActors
Indicates that certain actors were employed or utilized in performing an action, event, or production.
-
B.
majorActor
Indicates that the subject is a primary or leading participant in the action, event, or production involving the object.
-
C.
typicalCast
Indicates that the associated entities form the usual or characteristic cast of characters commonly appearing in a given work or type of work.
-
D.
typicalCasting
Indicates that one entity is the usual or standard casting choice for portraying another entity (such as a role, character, or type).
-
E.
originalCast
Indicates that the subject is a member of the initial group of performers or participants who first originated a role or production.
- 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a0309a4e4d481908a6070b40d507aae |
completed | May 12, 2026, 11:06 a.m. |
| PD | Predicate disambiguation | batch_6a03091ac1008190bf50357364d4e9e4 |
completed | May 12, 2026, 11:03 a.m. |
| PDg | Predicate description generation | batch_6a0309a3e5148190a07ab2a60529bafd |
completed | May 12, 2026, 11:06 a.m. |
Created at: April 29, 2026, 5:50 p.m.