Triple
T7172458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. 1st Army |
E167231
|
entity |
| Predicate | WWIComposition |
P43732
|
FINISHED |
| Object | American Expeditionary Forces component |
—
|
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: American Expeditionary Forces component | Statement: [U.S. 1st Army, WWIComposition, American Expeditionary Forces component]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: WWIComposition Context triple: [U.S. 1st Army, WWIComposition, American Expeditionary Forces component]
-
A.
worldWarIIService
Indicates that an entity served in some capacity during World War II.
-
B.
roleInWorldWarI
chosen
Indicates the specific function, position, or involvement an entity had during World War I.
-
C.
positionOnWorldWarI
Indicates a person’s or group’s stance, opinion, or policy regarding World War I.
-
D.
worldWar
Indicates a large-scale armed conflict involving multiple nations across different regions of the world, typically encompassing numerous battles, alliances, and theaters of war.
-
E.
alliedForcesComposition
Indicates the makeup and relative proportions of different military or paramilitary groups that are joined together as allied forces in a given context.
- 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_69c68889a2748190a316c5e65360361a |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e88b0a448190a19bd2d9e2a310a4 |
completed | March 27, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69c6e1ce5f048190808c378a980f7bb6 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:48 p.m.