Triple
T26007635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panthers in the Storm |
E646803
|
entity |
| Predicate | unitTypeDescribed |
P111029
|
FINISHED |
| Object | brigade combat team |
—
|
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: brigade combat team | Statement: [Panthers in the Storm, unitTypeDescribed, brigade combat team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unitTypeDescribed Context triple: [Panthers in the Storm, unitTypeDescribed, brigade combat team]
-
A.
typicalUnitType
Indicates that one entity is the standard or commonly used unit type associated with measuring or expressing the other entity.
-
B.
typeOfUnitStructure
chosen
Indicates that one unit is classified as having a particular structural type or organizational form.
-
C.
typeOfUnit
Indicates that one entity specifies the kind or category of measurement unit that the other entity belongs to.
-
D.
basedUnitType
Indicates that one unit is defined or derived in terms of another underlying (base) unit type.
-
E.
coreUnitType
Indicates that one entity is classified as the primary or fundamental type/category to which another entity (a core unit) belongs.
- 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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6057bd2708190bf400b153aca2f1b |
completed | May 2, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69f4a10728e08190bc0b96c558740f51 |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 9:01 a.m.