Triple
T28071706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Yemen republican forces |
E709419
|
entity |
| Predicate | receivedGroundForcesFrom |
P15397
|
FINISHED |
| Object | Egyptian Army |
—
|
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: Egyptian Army | Statement: [North Yemen republican forces, receivedGroundForcesFrom, Egyptian Army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivedGroundForcesFrom Context triple: [North Yemen republican forces, receivedGroundForcesFrom, Egyptian Army]
-
A.
suppliedTroopsTo
chosen
Indicates that one entity provided military personnel or forces to another entity.
-
B.
groundForces
Indicates that one entity deploys, commands, or involves military forces operating on land in relation to another entity or context.
-
C.
garrisonedForce
Indicates that a military force is stationed in and occupies a specific location, typically for defense or control.
-
D.
commandedForcesOf
Indicates that one entity held command authority over the military or armed forces associated with another entity.
-
E.
commandedForcesFrom
Indicates that one entity held command authority over military or organizational forces originating from another entity.
- 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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 8:46 p.m.