Triple
T37043041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 359th Infantry Regiment |
E916831
|
entity |
| Predicate | serviceStatusWWII |
P19660
|
FINISHED |
| Object | active combat unit |
—
|
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: active combat unit | Statement: [359th Infantry Regiment, serviceStatusWWII, active combat unit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceStatusWWII Context triple: [359th Infantry Regiment, serviceStatusWWII, active combat unit]
-
A.
statusDuringWorldWarII
chosen
Indicates the role, condition, or classification an entity had specifically during the period of World War II.
-
B.
worldWarIService
Indicates that an entity served or participated in military service during World War I.
-
C.
serviceBranchDuringWorldWarII
Indicates that an entity served in a specified branch of the military during World War II.
-
D.
serviceBranchDuringWorldWarI
Indicates that an entity served in a specified military branch during World War I.
-
E.
legalStatusDuringWWI
Indicates the legal condition or classification an entity held specifically during World War I (e.g., enemy alien, neutral, ally, civilian, combatant).
- 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_69f76e93ec4c8190be81cf87354d9155 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
Created at: May 3, 2026, 4:14 p.m.