Triple
T30850603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing 737-500 |
E785767
|
entity |
| Predicate | rangeWithTypicalPayload |
P170566
|
FINISHED |
| Object | approximately 4,444 km |
—
|
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: approximately 4,444 km | Statement: [Boeing 737-500, rangeWithTypicalPayload, approximately 4,444 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rangeWithTypicalPayload Context triple: [Boeing 737-500, rangeWithTypicalPayload, approximately 4,444 km]
-
A.
rangeWithFullPayload_km
Indicates the maximum distance, in kilometers, over which something can operate or travel while carrying its full intended payload.
-
B.
rangeSize
Indicates the extent or magnitude of the range over which something applies, varies, or is distributed.
-
C.
rangeType
Indicates the type or category of values that can appear in the range (output) position of a property or relation.
-
D.
rangeOf
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
-
E.
rangeVariant
Indicates that one entity is a variant or alternative form within the value range defined or covered by another entity.
- 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_69f224b850848190a4af4ccf8ddadcdf |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6917c8d8c8190b4091f3ef57834bb |
completed | May 3, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68fb914b88190b0cad83ea9fe9dfc |
completed | May 2, 2026, 11:58 p.m. |
Created at: April 29, 2026, 8:46 p.m.