Triple
T34253605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French 16th Division |
E878811
|
entity |
| Predicate | includedAttachedUnit |
P205384
|
FINISHED |
| Object | 369th Infantry Regiment |
E251699
|
NE 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: 369th Infantry Regiment | Statement: [French 16th Division, includedAttachedUnit, 369th Infantry Regiment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedAttachedUnit Context triple: [French 16th Division, includedAttachedUnit, 369th Infantry Regiment]
-
A.
includedUnitsFrom
Indicates that certain units are derived or taken from a larger set, collection, or source of units.
-
B.
usedAttachedUnitsFrom
Indicates that something is created or derived using units that are physically or logically attached to it.
-
C.
includedSingle
Indicates that one specific, individual item is contained within or made part of another set, group, or collection.
-
D.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
-
E.
basedUnitsInclude
Indicates that a composite or derived unit is defined using, and therefore includes, the specified base unit(s) in its construction.
- F. None of above. chosen
Provenance (5 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_69f349b421cc8190b4b4655e1d612548 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3786b89c608190980185e51ef4130f |
completed | June 21, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:56 a.m.