Triple
T18868784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yenangyaung |
E461511
|
entity |
| Predicate | involvedForcesInBattle |
P39448
|
FINISHED |
| Object | Allied forces |
—
|
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: Allied forces | Statement: [Yenangyaung, involvedForcesInBattle, Allied forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvedForcesInBattle Context triple: [Yenangyaung, involvedForcesInBattle, Allied forces]
-
A.
involvedForcesType
Indicates the type or category of forces that participate in or are associated with a given event, interaction, or situation.
-
B.
armedForcesInvolved
chosen
Indicates that the relationship or event involves the participation or presence of military or armed forces.
-
C.
engagedForces
Indicates that one force has actively committed or deployed its military units against another force in combat or operational interaction.
-
D.
numberOfTroopsInvolved
Indicates the quantity of military personnel participating in or assigned to a specific operation, event, or engagement.
-
E.
stateOfForces
Indicates the condition, disposition, or readiness level of military or organizational forces at a given time.
- 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c2a7e1308190a1667d2d2d43df6c |
completed | April 20, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69e48d2166b88190add38de96cedc65c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:57 a.m.