Triple
T28801255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaguchi Ube–Tokyo Haneda |
E727240
|
entity |
| Predicate | originPrefecture |
P100565
|
FINISHED |
| Object | Yamaguchi Prefecture |
—
|
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: Yamaguchi Prefecture | Statement: [Yamaguchi Ube–Tokyo Haneda, originPrefecture, Yamaguchi Prefecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originPrefecture Context triple: [Yamaguchi Ube–Tokyo Haneda, originPrefecture, Yamaguchi Prefecture]
-
A.
homePrefecture
Indicates the prefecture that an entity considers its home or place of origin.
-
B.
destinationPrefecture
Indicates the prefecture that serves as the destination location associated with an entity or event.
-
C.
hostPrefecture
Indicates the prefecture that serves as the host location for an event, activity, or entity.
-
D.
startingPrefecture
chosen
Indicates the prefecture in which something (such as a route, journey, or process) begins.
-
E.
hasPrefecture
Indicates that one administrative region or country possesses or is associated with a specific prefecture as a subordinate territorial unit.
- 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_69f0319b7c44819085736bcc256185e6 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69ff17be6ad48190963206f2619b1b28 |
completed | May 9, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69ff1724ba24819092c928fcbcb286ec |
completed | May 9, 2026, 11:14 a.m. |
Created at: April 28, 2026, 6:27 a.m.