Triple
T30182944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Pioneers |
E767250
|
entity |
| Predicate | roleInWarEffort |
P79144
|
FINISHED |
| Object | supporting British field armies |
—
|
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: supporting British field armies | Statement: [Black Pioneers, roleInWarEffort, supporting British field armies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInWarEffort Context triple: [Black Pioneers, roleInWarEffort, supporting British field armies]
-
A.
wartimeActivity
chosen
Indicates involvement in actions, roles, or operations specifically carried out during a period of war or armed conflict.
-
B.
roleInWorldWarI
Indicates the specific function, position, or involvement an entity had during World War I.
-
C.
strategicRoleDuringWar
Indicates that an entity served a particular strategic function or importance during a specific war or armed conflict.
-
D.
roleInWarOrConflict
Indicates the specific function, position, or involvement an entity has within a particular war or conflict.
-
E.
hasEmployerDuringWorldWarII
Indicates that an individual was employed by a specific employer during the time period of World War II.
- 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_69f2247cc3d88190811dec3face94bf5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ff49f888348190b9c55afa73b99e6a |
completed | May 9, 2026, 2:51 p.m. |
| PD | Predicate disambiguation | batch_69ff49614ef88190ac70b034c55ad738 |
completed | May 9, 2026, 2:49 p.m. |
Created at: April 29, 2026, 7:26 p.m.