Triple
T2333893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sikorsky Aircraft |
E44265
|
entity |
| Predicate | operatedInRole |
P37119
|
FINISHED |
| Object | defense contractor |
—
|
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: defense contractor | Statement: [Sikorsky Aircraft, operatedInRole, defense contractor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedInRole Context triple: [Sikorsky Aircraft, operatedInRole, defense contractor]
-
A.
operatedAs
Indicates that an entity functioned or was used in the capacity, role, or identity of another entity for some period of time.
-
B.
operatedAmong
Indicates that an entity carried out operations or activities within, or in coordination with, a specified group, set, or collection of other entities.
-
C.
operatedFor
Indicates that one entity performed operations or provided services on behalf of, or in support of, another entity for a certain period or purpose.
-
D.
servedInRole
chosen
Indicates that one entity performed duties or held a position within a specified role or office in relation to another entity.
-
E.
operatedBefore
Indicates that one entity performed an operation or action at an earlier time than another entity.
- 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_69a889132b488190bbb43ad4780ddd92 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abc6f75d888190a2e41edaa532e83f |
completed | March 7, 2026, 6:34 a.m. |
| PD | Predicate disambiguation | batch_69abc594087c819098100a10c5478a4b |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:51 p.m.