Triple
T17121062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voyager non-stop around-the-world flight aircraft |
E415464
|
entity |
| Predicate | notableFlightDuration |
P1526
|
FINISHED |
| Object | 9 days 3 minutes |
—
|
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: 9 days 3 minutes | Statement: [Voyager non-stop around-the-world flight aircraft, notableFlightDuration, 9 days 3 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFlightDuration Context triple: [Voyager non-stop around-the-world flight aircraft, notableFlightDuration, 9 days 3 minutes]
-
A.
flightDuration
chosen
Indicates the length of time that a specific flight takes from departure to arrival.
-
B.
dateOfNotableFlight
Indicates the calendar date on which a particular notable or significant flight took place.
-
C.
historicFlightDistance
Indicates the total distance that was covered during a past or completed flight.
-
D.
secondAroundTheWorldFlightDuration
Indicates the length of time taken to complete the second circumnavigation flight around the world.
-
E.
flightHours
Indicates the number of hours an entity has spent in flight or operating in the air.
- 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3e809ee888190a2cf69d59c0b9c20 |
completed | April 18, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69e35d6d20808190a38bb32e2294bc48 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:36 a.m.