Triple
T12458246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1. Armee |
E297716
|
entity |
| Predicate | hasUnitStructure |
P105112
|
FINISHED |
| Object | multiple army corps |
—
|
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: multiple army corps | Statement: [1. Armee, hasUnitStructure, multiple army corps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnitStructure Context triple: [1. Armee, hasUnitStructure, multiple army corps]
-
A.
hasUnitOf
Indicates that a quantity, measurement, or value is expressed in terms of a specific unit.
-
B.
hasSeparateUnit
Indicates that one entity exists or is treated as an independent, distinct unit from another entity.
-
C.
hasBasicUnit
Indicates that one entity is composed of, defined by, or fundamentally characterized through another entity that serves as its basic or minimal unit.
-
D.
hasUnitNumber
Indicates that an entity is associated with a specific unit identifier or number within a larger building, complex, or organizational structure.
-
E.
hasBasedUnits
Indicates that a derived measurement unit is defined in terms of one or more underlying base units.
- 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_69d6ada270808190b1a2b2e7b02bb426 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95151e7348190a1d4953a8b416a13 |
completed | April 10, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69d94d3c27a08190a0237200203e476d |
completed | April 10, 2026, 7:19 p.m. |
| PDg | Predicate description generation | batch_69d9511989ac8190ade98f52f66f7cd4 |
completed | April 10, 2026, 7:35 p.m. |
Created at: April 8, 2026, 9:56 p.m.