Triple
T26706921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diomedea exulans |
E673307
|
entity |
| Predicate | typicalFlightDistance |
P1525
|
FINISHED |
| Object | thousands of kilometres per foraging trip |
—
|
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: thousands of kilometres per foraging trip | Statement: [Diomedea exulans, typicalFlightDistance, thousands of kilometres per foraging trip]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFlightDistance Context triple: [Diomedea exulans, typicalFlightDistance, thousands of kilometres per foraging trip]
-
A.
laterFlightDistance
Indicates the distance associated with a flight that occurs later in time relative to another referenced flight.
-
B.
flightDistance
chosen
Indicates the measured distance covered by a flight between its origin and destination.
-
C.
firstFlightDistance
Indicates the distance covered during an entity’s first recorded flight.
-
D.
distanceToMBBAirport_km
Indicates the distance, measured in kilometers, from a given location to the MBB airport.
-
E.
distanceToAirport
Indicates the measured distance between a given location and the nearest or specified airport.
- 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_69eecda2b49c8190a6c481cfc4c07954 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69feecf1bb248190ba30f0bb1d22ee08 |
completed | May 9, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69feea5f27748190b223ee4e3ba5a678 |
completed | May 9, 2026, 8:03 a.m. |
Created at: April 27, 2026, 3:34 a.m.