Triple
T21622030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Army units |
E533600
|
entity |
| Predicate | hasSmallestTypicalElement |
P144813
|
FINISHED |
| Object | fire 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: fire team | Statement: [U.S. Army units, hasSmallestTypicalElement, fire team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSmallestTypicalElement Context triple: [U.S. Army units, hasSmallestTypicalElement, fire team]
-
A.
isSmallestOf
Indicates that an entity has the minimum size or value within a specified set or group of entities.
-
B.
isBoundedBelow
Indicates that every value in a set or function is greater than or equal to some fixed lower bound.
-
C.
isMinimumWhen
Indicates that a value or state is at its smallest or least level precisely under certain specified conditions or circumstances.
-
D.
hasMinimum
Indicates that an entity possesses at least a specified lower bound or smallest allowable value, quantity, or level in relation to another entity or constraint.
-
E.
hasFirstMinimumAt
Indicates that a function, sequence, or ordered set attains its first (earliest) minimum value at a specified position or element.
- 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_69e0c464fba881908d0ff2ac80511ce1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef3bafef548190b3856bfad1ebdc0b |
completed | April 27, 2026, 10:34 a.m. |
| PD | Predicate disambiguation | batch_69e69665fe8c8190af7e38785db188b2 |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69b4aa2b48190830107391e81571a |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:34 p.m.