Triple
T21819584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gekū |
E538688
|
entity |
| Predicate | relativeLocationToNaikū |
P145800
|
FINISHED |
| Object | about 6 kilometers from Naikū |
—
|
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: about 6 kilometers from Naikū | Statement: [Gekū, relativeLocationToNaikū, about 6 kilometers from Naikū]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeLocationToNaikū Context triple: [Gekū, relativeLocationToNaikū, about 6 kilometers from Naikū]
-
A.
mapLocation
Indicates a relationship where an entity is associated with a specific position or area on a map.
-
B.
locatedInDirectionFromTokyo
Indicates that one place is situated in a specified compass direction relative to Tokyo.
-
C.
relativeLocationWithinPisac
Indicates that one entity is located within the spatial or geographic boundaries of Pisac.
-
D.
ianaLocation
Indicates that an entity is associated with a specific geographic or network location identified using an IANA-defined naming or coding scheme.
-
E.
relativeLocationOnIsland
Indicates a spatial relationship where one entity’s position is described relative to another entity specifically in the context of being on an island.
- F. None of above. chosen
Provenance (4 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_69e0c475038c8190abb9b1a20eb8ff50 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f07cce0b8081909e20ded72db40304 |
completed | April 28, 2026, 9:24 a.m. |
| PD | Predicate disambiguation | batch_69e6be815a108190be81d7c987d0c0d6 |
completed | April 21, 2026, 12:02 a.m. |
| PDg | Predicate description generation | batch_69e6c670ee608190b9cfdc09de74f0de |
completed | April 21, 2026, 12:36 a.m. |
Created at: April 16, 2026, 6:54 p.m.