Triple
T2759029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tupolev Tu-104 |
E61174
|
entity |
| Predicate | landingRun |
P10875
|
FINISHED |
| Object | 1800 m |
—
|
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: 1800 m | Statement: [Tupolev Tu-104, landingRun, 1800 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landingRun Context triple: [Tupolev Tu-104, landingRun, 1800 m]
-
A.
landing
Indicates the action or event of an entity coming down from the air or a higher position to make controlled contact with a surface.
-
B.
landingMethod
Indicates the manner or technique by which something or someone arrives and comes to rest at a destination, typically from the air or space.
-
C.
landingArea
Indicates that a location or surface serves as a designated area where something (such as an aircraft, object, or person) can land.
-
D.
landingDistance
chosen
Indicates the required or actual distance needed for an aircraft or object to complete a landing from approach to full stop.
-
E.
landingAttemptResult
Indicates the outcome or status of an attempted landing action, such as whether the landing succeeded, failed, or had another specific result.
- 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_69ab4b7a85bc819094a349b84beb1f2c |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb8d34f88190a760111fe303cf24 |
completed | March 7, 2026, 8:02 a.m. |
| PD | Predicate disambiguation | batch_69abd82de7f48190acd614f28644c6da |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:57 p.m.