Triple
T18139731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 167th Mission Support Group |
E434228
|
entity |
| Predicate | hasSubordinateFunction |
P130600
|
FINISHED |
| Object | logistics |
—
|
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: logistics | Statement: [167th Mission Support Group, hasSubordinateFunction, logistics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubordinateFunction Context triple: [167th Mission Support Group, hasSubordinateFunction, logistics]
-
A.
hasSubrole
Indicates that one role functions as a more specific, subordinate, or specialized version of another broader role.
-
B.
hasSubConcept
Indicates that one concept is a more specific, subordinate, or narrower idea within the scope of another, more general concept.
-
C.
hasSubfacility
Indicates that one facility is a subordinate or component facility within another, larger facility.
-
D.
hasSubService
Indicates that one service includes or is composed of another, more specific service as a subordinate or component part.
-
E.
hasSubordinateCommand
Indicates that one command or unit holds authority over and directs the operations of another command or unit that is subordinate to it.
- 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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4de0a59d08190be74c1ecc00a8f3a |
completed | April 19, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f5ae2c8190b11dee46534fa5a9 |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:29 a.m.