Triple
T37040351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing 737-400 |
E916761
|
entity |
| Predicate | cargoConversionVariant |
P117575
|
FINISHED |
| Object | Boeing 737-400SF |
—
|
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: Boeing 737-400SF | Statement: [Boeing 737-400, cargoConversionVariant, Boeing 737-400SF]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cargoConversionVariant Context triple: [Boeing 737-400, cargoConversionVariant, Boeing 737-400SF]
-
A.
propulsionTypeVariant
Indicates a relationship where one propulsion type is a specific variant or subtype of another propulsion type.
-
B.
conversionOfShip
Indicates the process by which a ship is altered or transformed from one configuration, role, or specification into another.
-
C.
resultedInVehicleVariant
chosen
Indicates that one event, process, or action led to the creation or emergence of a specific variant of a vehicle.
-
D.
carTypeVariant
Indicates that one car type is a specific variant or version of another car type.
-
E.
hasTrackbedConversion
Indicates that a trackbed has been converted from its original railway use to another type of use or infrastructure.
- 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_69f76e93ec4c8190be81cf87354d9155 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.