Triple
T22924923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lin Biao incident |
E569275
|
entity |
| Predicate | flightRouteAttempted |
P10707
|
FINISHED |
| Object | China to Soviet Union |
—
|
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: China to Soviet Union | Statement: [Lin Biao incident, flightRouteAttempted, China to Soviet Union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flightRouteAttempted Context triple: [Lin Biao incident, flightRouteAttempted, China to Soviet Union]
-
A.
flightRoute
chosen
Indicates a path or sequence of locations that a particular flight travels between, typically from its origin to its destination (and possibly via intermediate stops).
-
B.
flightOver
Indicates that one entity moves through the air above or across another entity or area.
-
C.
flightRecord
Indicates a record of a specific flight event or journey, capturing details about its occurrence and characteristics.
-
D.
performedFlightTo
Indicates that an entity (such as an aircraft or airline) carried out a flight whose destination was a specified location.
-
E.
investigatesFlight
Indicates that an entity conducts an inquiry or examination into a specific flight or flight-related incident.
- 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_69e2458f7d008190901dccbaebeaba24 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f180d84fc08190b747c3f9052c657a |
completed | April 29, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69ef3b7c5fc081909ac50c5c8569cc19 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:43 p.m.