Triple
T34033091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cessna 206 |
E872711
|
entity |
| Predicate | engineManufacturerTypical |
P2092
|
FINISHED |
| Object | Textron Lycoming |
—
|
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: Textron Lycoming | Statement: [Cessna 206, engineManufacturerTypical, Textron Lycoming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineManufacturerTypical Context triple: [Cessna 206, engineManufacturerTypical, Textron Lycoming]
-
A.
engineManufacturerTested
Indicates that an engine manufacturer has been subjected to and has undergone a testing or evaluation process.
-
B.
typicalEngineCharacteristic
Indicates that the specified property or feature is a characteristic commonly or typically associated with the given engine.
-
C.
typicalEngine
chosen
Indicates that an entity is the standard or commonly used engine for another entity (such as a vehicle, device, or system).
-
D.
engineBrand
Indicates that one entity is the brand or manufacturer of the engine used by another entity.
-
E.
engineUsedIn
Indicates that a particular engine is utilized as a component or power source within a specified system, device, or application.
- 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_69f349a2527c81909a7cd4bda94d70ad |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:51 a.m.