Triple
T5008696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airco DH.9 |
E112559
|
entity |
| Predicate | serviceEntryIssue |
P13650
|
FINISHED |
| Object | high loss rates due to engine problems |
—
|
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: high loss rates due to engine problems | Statement: [Airco DH.9, serviceEntryIssue, high loss rates due to engine problems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceEntryIssue Context triple: [Airco DH.9, serviceEntryIssue, high loss rates due to engine problems]
-
A.
serviceEntryStatus
Indicates the current state or condition of a service entry within a process or system (e.g., whether it is active, pending, completed, or otherwise classified).
-
B.
facingIssue
chosen
Indicates that an entity is currently experiencing, encountering, or dealing with a problem, difficulty, or obstacle.
-
C.
serviceSystem
Indicates a relationship where one entity functions as a service system that provides, manages, or supports services for another entity.
-
D.
laterOperationalIssue
Indicates that an operational issue occurred at some point after a referenced time, event, or condition.
-
E.
serviceEntryContext
Indicates the contextual circumstances or environment in which a particular service entry is created, recorded, or applied.
- 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_69bd4433d0b08190877e83959ef40d81 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd730a7590819088ab8d49c5c88c2f |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd714cbc448190aa53a8a83d768b64 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:35 p.m.