Triple
T12354747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | India Theater |
E294581
|
entity |
| Predicate | primaryAlliedObjective |
P104621
|
FINISHED |
| Object | recapture of Burma |
—
|
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: recapture of Burma | Statement: [India Theater, primaryAlliedObjective, recapture of Burma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAlliedObjective Context triple: [India Theater, primaryAlliedObjective, recapture of Burma]
-
A.
secretObjective
Indicates that an entity has a hidden or undisclosed goal or target that is not known to others.
-
B.
opponentObjective
Indicates that one entity is the target or goal that an opposing entity aims to counter, defeat, or prevent from succeeding.
-
C.
primaryAlly
Indicates that one entity is the main or most significant ally or supportive partner of another entity.
-
D.
insurgentObjective
Indicates that an insurgent group or actor has a specific strategic goal, target, or desired outcome they are attempting to achieve.
-
E.
primaryMissionTo
Indicates that an entity has a main or principal mission directed toward or focused on another entity.
- 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_69d6ab6ccbec8190b09e2d357aa80064 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f8bc60c8190b0ceb84093e70db4 |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ecb5efc819086a3530282278bb1 |
completed | April 10, 2026, 6:17 p.m. |
| PDg | Predicate description generation | batch_69d93f607a88819089e89fd263ae9937 |
completed | April 10, 2026, 6:20 p.m. |
Created at: April 8, 2026, 9:54 p.m.