Triple
T34213384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 140th Maintenance Group |
E877718
|
entity |
| Predicate | hasSubordinateElementType |
P38626
|
FINISHED |
| Object | maintenance squadrons |
—
|
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: maintenance squadrons | Statement: [140th Maintenance Group, hasSubordinateElementType, maintenance squadrons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubordinateElementType Context triple: [140th Maintenance Group, hasSubordinateElementType, maintenance squadrons]
-
A.
hasElementType
Indicates that something is composed of or contains elements that are of a specified type.
-
B.
hasSubcomponent
Indicates that one entity is a constituent part or component of another, larger entity.
-
C.
hasSubordinateFunction
Indicates that one function operates under the authority, control, or scope of another function as its subordinate.
-
D.
hasSubOrganizationType
chosen
Indicates that an organization is associated with or classified under a specific type or category of sub-organization.
-
E.
hasSubproperty
Indicates that one property is a more specific version of another property, inheriting its meaning and constraints.
- 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_69f349b0b4bc819088c1552424089ee9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff891e4b9c8190aa86a339a8944496 |
completed | May 9, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69ff8801180c8190b23e20996ca68e0a |
completed | May 9, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:55 a.m.