Triple
T35701457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clyde Pangborn |
E1031595
|
entity |
| Predicate | startLocationOfHistoricFlight |
P127110
|
FINISHED |
| Object | Sabishiro Beach, Misawa, Aomori, Japan |
—
|
NE NERFINISHED |
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: Sabishiro Beach, Misawa, Aomori, Japan | Statement: [Clyde Pangborn, startLocationOfHistoricFlight, Sabishiro Beach, Misawa, Aomori, Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startLocationOfHistoricFlight Context triple: [Clyde Pangborn, startLocationOfHistoricFlight, Sabishiro Beach, Misawa, Aomori, Japan]
-
A.
directionOfHistoricFlight
Indicates the compass direction or route orientation taken by a historically significant flight.
-
B.
historicFlightDistance
Indicates the total distance that was covered during a past or completed flight.
-
C.
originOfFlight
chosen
Indicates that one location serves as the starting point or departure place for a particular flight.
-
D.
allegedFirstFlightPlace
Indicates the location where an entity is claimed or reported to have made its first flight, without asserting that the claim is definitively true.
-
E.
firstFlightLaunchSite
Indicates the location where an entity’s first flight was launched.
- 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_69f76e0d393c8190b6303c64408736db |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0082989e6c819099fea0e706332e37 |
completed | May 10, 2026, 1:05 p.m. |
| PD | Predicate disambiguation | batch_6a0081ed6a1481908baf472876e28db9 |
completed | May 10, 2026, 1:02 p.m. |
Created at: May 3, 2026, 4:05 p.m.