Triple
T17366840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fiji Military Forces |
E422206
|
entity |
| Predicate | hasTrainingRelationshipWith |
P36609
|
FINISHED |
| Object | foreign militaries |
—
|
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: foreign militaries | Statement: [Fiji Military Forces, hasTrainingRelationshipWith, foreign militaries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrainingRelationshipWith Context triple: [Fiji Military Forces, hasTrainingRelationshipWith, foreign militaries]
-
A.
hasTrainingFor
Indicates that an entity has received or possesses training that prepares it for performing a specific task, role, or function.
-
B.
hasTrainingRole
Indicates that an entity holds or is assigned a specific role within a training or instructional context.
-
C.
hasTrainingType
Indicates that an entity is associated with or characterized by a specific type or category of training.
-
D.
hasTrainingTrack
Indicates that an entity is associated with or assigned to a specific training track or program.
-
E.
hasTrained
chosen
Indicates that one entity has provided training or instruction to 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a661fc08190a4c386125bddb16b |
completed | April 19, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.