Triple
T31597237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Embraer Praetor 500 |
E806249
|
entity |
| Predicate | fuelCapacity_liters |
P19393
|
FINISHED |
| Object | approximately 9340 |
—
|
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 9340 | Statement: [Embraer Praetor 500, fuelCapacity_liters, approximately 9340]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuelCapacity_liters Context triple: [Embraer Praetor 500, fuelCapacity_liters, approximately 9340]
-
A.
fuelCapacityLiters
chosen
Indicates the amount of fuel a vehicle or container can hold, measured in liters.
-
B.
fuelCapacityKg
Indicates the maximum amount of fuel an entity can hold, measured in kilograms.
-
C.
fuelTankConfiguration
Indicates how a system’s fuel tanks are arranged, connected, or structured relative to one another.
-
D.
mainTankCapacity
Indicates the maximum volume of fuel or liquid that the primary tank is designed to hold.
-
E.
hasFuelStorage
Indicates that one entity possesses or is equipped with a facility, container, or system used to store fuel for later use.
- 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_69f348d54ccc8190a03b5df9a2b40b25 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a835ecc48190912306b14b3e2909 |
completed | May 3, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:31 p.m.