Triple
T31781106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snecma |
E811202
|
entity |
| Predicate | suppliesEngineFor |
P17328
|
FINISHED |
| Object | Airbus A320 family |
—
|
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: Airbus A320 family | Statement: [Snecma, suppliesEngineFor, Airbus A320 family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suppliesEngineFor Context triple: [Snecma, suppliesEngineFor, Airbus A320 family]
-
A.
engineSupplier
chosen
Indicates a relationship where one entity supplies or provides engines to another entity.
-
B.
developedEngine
Indicates that one entity created, designed, or engineered an engine for another entity or purpose.
-
C.
associatedWithEngine
Indicates a relationship in which something is connected, linked, or related to an engine, typically through use, function, or dependency.
-
D.
spitfireEngineSupplier
Indicates that an entity serves as the engine supplier for a Spitfire aircraft.
-
E.
rocketEngineSupplier
Indicates that one entity supplies rocket engines to 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_69f348e544a48190ab6e700b05f6438c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:36 p.m.