Triple
T35455757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 土佐国 |
E1024767
|
entity |
| Predicate | modernPrefectureCorrespondence |
P193681
|
FINISHED |
| Object | ほぼ高知県に相当する |
—
|
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: ほぼ高知県に相当する | Statement: [土佐国, modernPrefectureCorrespondence, ほぼ高知県に相当する]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernPrefectureCorrespondence Context triple: [土佐国, modernPrefectureCorrespondence, ほぼ高知県に相当する]
-
A.
prefectureOfHeadquarters
Indicates the administrative prefecture in which an organization's headquarters is located.
-
B.
prefectureRepresentation
Indicates that one entity serves as the official representative body or office for a given prefecture within a governmental or administrative context.
-
C.
accessPrefecture
Indicates that an entity has access to, or is associated with accessing, a specific prefecture.
-
D.
hasPrefecturalOffice
Indicates that a given location or administrative unit contains or hosts an official prefectural government office.
-
E.
isPrefecture
Indicates that one entity functions as an administrative prefecture governing or representing the other entity.
- 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_69f76df92f108190817222e520e22268 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
| PDg | Predicate description generation | batch_69fd4f38728c8190b3271abc80882cfb |
completed | May 8, 2026, 2:49 a.m. |
Created at: May 3, 2026, 4:04 p.m.