Triple
T34538066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ebina Service Area |
E886724
|
entity |
| Predicate | hasNearbyPrefectureCapital |
P60387
|
FINISHED |
| Object | Yokohama |
—
|
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: Yokohama | Statement: [Ebina Service Area, hasNearbyPrefectureCapital, Yokohama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyPrefectureCapital Context triple: [Ebina Service Area, hasNearbyPrefectureCapital, Yokohama]
-
A.
prefectureCapitalNearby
chosen
Indicates that a prefecture’s capital city is geographically close to the referenced location.
-
B.
hasNearbyPrefecture
Indicates that one administrative region has another prefecture located geographically close to it.
-
C.
isInPrefecturalCapital
Indicates that one entity is located within the administrative boundaries of a prefectural capital city.
-
D.
isNearCapitalCity
Indicates that an entity is located close to, or in the immediate vicinity of, a capital city.
-
E.
prefectureCapitalDistance
Indicates the distance between a prefecture and its designated capital city.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ffde9263248190996f970b6cf6e49d |
completed | May 10, 2026, 1:25 a.m. |
| PD | Predicate disambiguation | batch_69ffdd760f1c8190abc6c0c1cd97ba5f |
completed | May 10, 2026, 1:20 a.m. |
Created at: May 1, 2026, 2:02 a.m.