Triple
T30442430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokyo (Narita) – Okinawa (Naha) |
E774485
|
entity |
| Predicate | geographicEndpointNorth |
P136613
|
FINISHED |
| Object | Honshu |
—
|
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: Honshu | Statement: [Tokyo (Narita) – Okinawa (Naha), geographicEndpointNorth, Honshu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicEndpointNorth Context triple: [Tokyo (Narita) – Okinawa (Naha), geographicEndpointNorth, Honshu]
-
A.
northernmostPoint
chosen
Indicates the location that lies furthest to the north within the spatial extent of a given entity.
-
B.
isNorthernmost
Indicates that one entity is located farther north than all other comparable entities in a given set or region.
-
C.
isNorthernmostRegionOf
Indicates that one region is the geographically furthest north among all regions within a specified larger area or entity.
-
D.
locatedNorthOf
Indicates that one entity is positioned geographically to the north of another entity.
-
E.
containsNorthCelestialPole
Indicates that the referenced region or object in the sky includes the position of the north celestial pole within its boundaries.
- 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_69f22493ef9c8190ae8c2afcb7f994c8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 29, 2026, 8:08 p.m.