Triple
T8182675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heinkel He 59 |
E191103
|
entity |
| Predicate | hasFloatConfiguration |
P13644
|
FINISHED |
| Object | twin-float seaplane |
—
|
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: twin-float seaplane | Statement: [Heinkel He 59, hasFloatConfiguration, twin-float seaplane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFloatConfiguration Context triple: [Heinkel He 59, hasFloatConfiguration, twin-float seaplane]
-
A.
hasConfiguration
chosen
Indicates that an entity is associated with or defined by a particular configuration or setup.
-
B.
isFloatingCurrency
Indicates that a currency’s value is determined by market forces and allowed to fluctuate freely rather than being fixed to another asset or currency.
-
C.
hasAxisConfiguration
Indicates that one entity specifies or defines the axis arrangement, orientation, or setup used by another entity.
-
D.
hasConfigurationFile
Indicates that an entity is associated with or defined by a specific configuration file.
-
E.
hasFraction
Indicates that one entity represents a fractional part or proportion of another entity.
- 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_69ca82c4538081909404325aa5639483 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4c4db8748190aa785e0c70fac497 |
completed | March 31, 2026, 4:23 a.m. |
| PD | Predicate disambiguation | batch_69cb36a7952481908f34e3e82f375a84 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:40 p.m.