Triple
T34836318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Babur-2 |
E1004209
|
entity |
| Predicate | hasFlightProfile |
P134910
|
FINISHED |
| Object | subsonic |
—
|
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: subsonic | Statement: [Babur-2, hasFlightProfile, subsonic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFlightProfile Context triple: [Babur-2, hasFlightProfile, subsonic]
-
A.
intendedFlightProfile
Indicates the planned or expected way an aircraft is supposed to fly a mission, including its route, altitude, speed, and other flight parameters.
-
B.
hasFlightCharacteristic
chosen
Indicates that an entity possesses a specific property, quality, or behavior related to flight.
-
C.
hasFlightNumber
Indicates that a specific flight is identified or labeled by a particular flight number.
-
D.
isFlownWith
Indicates that one entity travels by air together with, or using the same flight as, another entity.
-
E.
hasFlownIn
Indicates that an entity has previously traveled by flying in or on another entity (such as an aircraft or similar vehicle).
- 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_69f76db97714819099b5bed36fd64e9d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.