Triple
T33924611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sud Aviation Super-Caravelle |
E869712
|
entity |
| Predicate | designPhaseOutcome |
P126837
|
FINISHED |
| Object | superseded by joint Concorde configuration |
—
|
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: superseded by joint Concorde configuration | Statement: [Sud Aviation Super-Caravelle, designPhaseOutcome, superseded by joint Concorde configuration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designPhaseOutcome Context triple: [Sud Aviation Super-Caravelle, designPhaseOutcome, superseded by joint Concorde configuration]
-
A.
designOutcome
chosen
Indicates the result, effect, or consequence produced by a particular design or design process.
-
B.
designCompletion
Indicates that the design phase of something has been finished or brought to completion.
-
C.
designStatus
Indicates the current state or phase of progress for a design within its lifecycle.
-
D.
designStep
Indicates a specific stage or phase within a broader design process or workflow.
-
E.
designProcess
Indicates the sequence of actions, decisions, and iterations involved in creating, developing, or refining a design.
- 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_69f349992c508190aa4afa24a086cc8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fec25f0fc48190b87ab1f9cd1eb0de |
completed | May 9, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69fec079a770819098df7cc3049df954 |
completed | May 9, 2026, 5:04 a.m. |
Created at: May 1, 2026, 1:49 a.m.