Triple
T37694419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alpine Div. |
E938888
|
entity |
| Predicate | hasTypicalUnitType |
P41758
|
FINISHED |
| Object | infantry division |
—
|
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: infantry division | Statement: [Alpine Div., hasTypicalUnitType, infantry division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalUnitType Context triple: [Alpine Div., hasTypicalUnitType, infantry division]
-
A.
typicalUnitType
chosen
Indicates that one entity is the standard or commonly used unit type associated with measuring or expressing the other entity.
-
B.
typicalSupportedUnitType
Indicates the kind or category of unit that an entity is normally designed or expected to support.
-
C.
hasTypicalUsageType
Indicates that something is associated with a standard or commonly expected way in which it is used.
-
D.
hasBasicUnit
Indicates that one entity is composed of, defined by, or fundamentally characterized through another entity that serves as its basic or minimal unit.
-
E.
hasUnitStructure
Indicates that an entity possesses a specific internal organization or arrangement that defines its structural composition.
- 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_69f76eda6ae48190b3111071eeacc038 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fff4530f908190afe9387f732c2b7e |
completed | May 10, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69fff3c01a64819091196875b0c88607 |
completed | May 10, 2026, 2:56 a.m. |
Created at: May 3, 2026, 4:18 p.m.