Triple
T17593650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 113th Maintenance Group |
E428507
|
entity |
| Predicate | equipmentMaintained |
P90358
|
FINISHED |
| Object | military aircraft |
—
|
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: military aircraft | Statement: [113th Maintenance Group, equipmentMaintained, military aircraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equipmentMaintained Context triple: [113th Maintenance Group, equipmentMaintained, military aircraft]
-
A.
hasMaintenance
Indicates that an entity is subject to, associated with, or requires a particular maintenance activity or maintenance record.
-
B.
maintenanceType
Indicates the specific category or kind of maintenance activity associated with an entity or relationship.
-
C.
canMaintain
chosen
Indicates that one entity has the ability or capacity to maintain, service, or keep another entity in proper working condition.
-
D.
hasMaintenanceService
Indicates that an entity receives or is covered by a maintenance service provided by another entity.
-
E.
maintenanceStatus
Indicates the current state or condition of an entity with respect to its maintenance activities, such as whether it is pending, in progress, completed, or overdue.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e469e89acc81908e52138ad4f452c6 |
completed | April 19, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:51 a.m.