Triple
T34180772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cessna 310 |
E876807
|
entity |
| Predicate | firstCustomerDeliveries |
P205352
|
FINISHED |
| Object | mid-1950s |
—
|
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: mid-1950s | Statement: [Cessna 310, firstCustomerDeliveries, mid-1950s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstCustomerDeliveries Context triple: [Cessna 310, firstCustomerDeliveries, mid-1950s]
-
A.
firstDeliveryDate
Indicates the date on which an item, service, or order is delivered for the first time.
-
B.
initialCustomers
Indicates that the referenced entities are customers present or involved at the starting point of a process, period, or system.
-
C.
delivers
Indicates that one entity transports or hands over something to another entity as intended or required.
-
D.
deliveredBy
Indicates that something (such as a product, message, or service) is brought, transported, or provided to its destination by a specified agent or carrier.
-
E.
deliveredWith
Indicates that one item, service, or message is brought or transported to a recipient together with another, as part of the same delivery.
- 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_69f349ae640c8190b9cd220b5368d8b6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:54 a.m.