Triple
T750101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heinkel He 177 |
E15427
|
entity |
| Predicate | maxTakeoffWeight |
P10870
|
FINISHED |
| Object | 31500 kg |
—
|
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: 31500 kg | Statement: [Heinkel He 177, maxTakeoffWeight, 31500 kg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxTakeoffWeight Context triple: [Heinkel He 177, maxTakeoffWeight, 31500 kg]
-
A.
maximumTakeoffWeight
chosen
Indicates the greatest allowable weight an aircraft can have at the start of its takeoff roll under specified conditions.
-
B.
takeoffDistanceAtMaxWeight
Indicates the distance required for an aircraft to take off when operating at its maximum allowable weight.
-
C.
maximumPayload
Indicates the greatest amount of load or capacity that an entity is designed or allowed to carry, handle, or support.
-
D.
maximumPassengerCapacity
Indicates the greatest number of passengers that an entity is designed or allowed to carry at one time.
-
E.
maximumWeight
Indicates the greatest allowable or observed weight value associated with an entity or relationship.
- 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_69a493599a0081908da65f3407af1ef2 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a6304e0c8190827fb57c5cac2da9 |
completed | March 1, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69a4a5004f708190a984ee221716e19c |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.