Triple
T25715433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London–Tokyo |
E644848
|
entity |
| Predicate | overfliesRegion |
P121855
|
FINISHED |
| Object | Arctic region |
—
|
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: Arctic region | Statement: [London–Tokyo, overfliesRegion, Arctic region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overfliesRegion Context triple: [London–Tokyo, overfliesRegion, Arctic region]
-
A.
flownOver
chosen
Indicates that one entity has moved through the air above or across another entity or location.
-
B.
crossesRegion
Indicates that an entity moves through or passes across the spatial extent of a specified region.
-
C.
flybyOf
Indicates that one entity passes close to another in space without stopping, typically as part of an observational or transit maneuver.
-
D.
flightOver
Indicates that one entity moves through the air above or across another entity or area.
-
E.
overField
Indicates a spatial relationship where one entity is positioned above or extends across the area of a field.
- 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fc6211788190bb46c645902c2bc2 |
completed | May 2, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 9:40 p.m.