Triple
T28221857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Renton Final Assembly |
E711476
|
entity |
| Predicate | transportModeForDelivery |
P1379
|
FINISHED |
| Object | air |
—
|
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: air | Statement: [Renton Final Assembly, transportModeForDelivery, air]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportModeForDelivery Context triple: [Renton Final Assembly, transportModeForDelivery, air]
-
A.
transportModeTo
Indicates the means or mode of transportation used to travel to a specified destination.
-
B.
transportModePresent
Indicates that a particular mode of transportation is involved or available in the described context or event.
-
C.
deliveryModelOf
Indicates that one entity functions as the delivery model or mechanism through which another entity (such as a service, product, or program) is provided or made available.
-
D.
transportType
chosen
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
-
E.
intendedCarryMethod
Indicates the manner or method by which something is meant or designed to be carried.
- 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_69efb51dfb048190ada79b745c33b363 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: April 27, 2026, 10:47 p.m.