Triple
T37043051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 359th Infantry Regiment |
E916831
|
entity |
| Predicate | continentOfOperationsWWII |
P194884
|
FINISHED |
| Object | Europe |
—
|
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: Europe | Statement: [359th Infantry Regiment, continentOfOperationsWWII, Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continentOfOperationsWWII Context triple: [359th Infantry Regiment, continentOfOperationsWWII, Europe]
-
A.
sideInWorldWarII
Indicates that an entity was aligned with or participated on a particular side during World War II.
-
B.
countryDuringWar
Indicates that a country exists or participates as a relevant actor during a specified war or armed conflict.
-
C.
contestedByDuringWWII
Indicates that the entities were in opposition or conflict with each other during World War II.
-
D.
worldWarIPartOf
Indicates that an event or entity is a component, phase, or subset of World War I.
-
E.
worldWarITheaterCountry
Indicates that a country was a location or participant in a specific theater of operations during World War I.
- F. None of above. chosen
Provenance (4 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_69f76e93ec4c8190be81cf87354d9155 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
| PDg | Predicate description generation | batch_69fd8ccaee848190acd59d7d643ad062 |
completed | May 8, 2026, 7:12 a.m. |
Created at: May 3, 2026, 4:14 p.m.