Triple
T34253604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French 16th Division |
E878811
|
entity |
| Predicate | usedAttachedUnitsFrom |
P196336
|
FINISHED |
| Object | United States |
—
|
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: United States | Statement: [French 16th Division, usedAttachedUnitsFrom, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAttachedUnitsFrom Context triple: [French 16th Division, usedAttachedUnitsFrom, United States]
-
A.
hasUnitsFrom
Indicates that one entity derives, adopts, or uses its measurement units from another specified source entity.
-
B.
associatedWithUnit
Indicates that one entity has a connection, linkage, or affiliation with a particular unit (such as a division, department, or organizational subunit).
-
C.
associatedUnitType
Indicates that one entity is linked to or characterized by a particular type or category of unit.
-
D.
isPeripheralUnitOf
Indicates that one unit functions as a subsidiary or outer component belonging to, and typically supporting, a larger central unit.
-
E.
attachedTo
Indicates that one entity is physically or logically fastened, connected, or joined to another entity.
- 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_69f349b421cc8190b4b4655e1d612548 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe21b0cba48190b56c39e9f1c0eafa |
completed | May 8, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69fe204576848190aecf204e2adba5dc |
completed | May 8, 2026, 5:41 p.m. |
| PDg | Predicate description generation | batch_69fe21afdc4c8190913ac4b55a9a5f52 |
completed | May 8, 2026, 5:47 p.m. |
Created at: May 1, 2026, 1:56 a.m.