Triple
T29658339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Electric YF120 |
E750331
|
entity |
| Predicate | testApplication |
P167574
|
FINISHED |
| Object | YF-22 prototype |
—
|
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: YF-22 prototype | Statement: [General Electric YF120, testApplication, YF-22 prototype]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testApplication Context triple: [General Electric YF120, testApplication, YF-22 prototype]
-
A.
exampleApplication
Indicates that something serves as a representative or illustrative instance of how an application is used or functions.
-
B.
appliedTest
Indicates that a test has been administered or carried out on a particular subject or object.
-
C.
test
Indicates that an entity performs, undergoes, or is associated with a testing or examination process involving another entity or condition.
-
D.
applicationInterface
Indicates that one entity serves as an interface or interaction layer through which another entity accesses or uses an application’s functionality.
-
E.
testingMethod
Indicates the procedure, technique, or approach used to perform a particular test or evaluation.
- F. None of above. chosen
Provenance (4 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_69f66f2939608190b987081b44b2fefd |
completed | May 2, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 6:56 p.m.