Triple
T26766605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armored Brigade Combat Team |
E674955
|
entity |
| Predicate | hasTypicalSubunit |
P112029
|
FINISHED |
| Object | combined arms battalion |
—
|
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: combined arms battalion | Statement: [Armored Brigade Combat Team, hasTypicalSubunit, combined arms battalion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalSubunit Context triple: [Armored Brigade Combat Team, hasTypicalSubunit, combined arms battalion]
-
A.
typicalSubunitOf
chosen
Indicates that something is a standard or commonly occurring subcomponent or part of a larger whole.
-
B.
hasSubunits
Indicates that an entity is composed of or organized into smaller constituent units that are part of its structure.
-
C.
usesSameSubunitStructureAs
Indicates that two entities share an identical or equivalent arrangement and composition of their constituent subunits within a larger structural framework.
-
D.
hasSubunitName
Indicates that an entity includes or is associated with a named subunit or component as part of its structure or organization.
-
E.
subunitType
Indicates that one entity is a specific kind or classification of subunit within the structure or composition of another entity.
- 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_69eecda85298819097ee1c38a3d772e7 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 27, 2026, 4 a.m.