Triple
T29658338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Electric YF120 |
E750331
|
entity |
| Predicate | intendedProductionApplication |
P160466
|
FINISHED |
| Object | F-22 Raptor |
—
|
NE NERFINISHED |
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: F-22 Raptor | Statement: [General Electric YF120, intendedProductionApplication, F-22 Raptor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedProductionApplication Context triple: [General Electric YF120, intendedProductionApplication, F-22 Raptor]
-
A.
isIntendedForUseBy
chosen
Indicates that something is designed, meant, or purposed to be used by a particular entity or group.
-
B.
inProduction
Indicates that something is currently being created, manufactured, or developed but is not yet completed or released.
-
C.
targetProduction
Indicates a relationship where one entity is the intended or designated output, result, or product generated by another entity or process.
-
D.
hasProductionUse
Indicates that something is utilized or applied within a production or operational environment.
-
E.
designedForProductionBy
Indicates that something has been created or configured specifically to be manufactured or produced by a particular agent or organization.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: April 28, 2026, 6:56 p.m.