Triple
T37871538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Convair 580 |
E944616
|
entity |
| Predicate | improvedPerformanceComparedTo |
P6555
|
FINISHED |
| Object | Convair CV‑340 |
—
|
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: Convair CV‑340 | Statement: [Convair 580, improvedPerformanceComparedTo, Convair CV‑340]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: improvedPerformanceComparedTo Context triple: [Convair 580, improvedPerformanceComparedTo, Convair CV‑340]
-
A.
improvesOn
chosen
Indicates that one entity enhances, refines, or performs better than another entity, typically by addressing its limitations or increasing its effectiveness.
-
B.
comparedToPredecessor
Indicates that something is being evaluated or measured in relation to the thing that came immediately before it.
-
C.
performanceImprovementReason
Indicates the reason or cause behind an observed or intended improvement in performance.
-
D.
hasImproved
Indicates that an entity’s state, quality, or performance has become better compared to a previous point in time.
-
E.
isMoreEfficientThan
Indicates that one entity performs a task or uses resources in a way that achieves the same or better outcome with less time, effort, or cost than 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.