Triple
T33252599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikawa region |
E851289
|
entity |
| Predicate | positionWithinPrefecture |
P82824
|
FINISHED |
| Object | eastern Aichi 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: eastern Aichi Prefecture | Statement: [Mikawa region, positionWithinPrefecture, eastern Aichi Prefecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionWithinPrefecture Context triple: [Mikawa region, positionWithinPrefecture, eastern Aichi Prefecture]
-
A.
locatedInPrefectureLevel
Indicates that one entity is geographically situated within, and administratively belongs to, a specific prefecture-level jurisdiction.
-
B.
locatedInRegionOfPrefecture
chosen
Indicates that one entity is geographically situated within a specific region that belongs to or is administered as part of a given prefecture.
-
C.
accessPrefecture
Indicates that an entity has access to, or is associated with accessing, a specific prefecture.
-
D.
isPrefecture
Indicates that one entity functions as an administrative prefecture governing or representing the other entity.
-
E.
passesPrefecture
Indicates that a route, path, or entity traverses through or goes across a specified prefecture.
- 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_69f34963135c819084e7f1d483421f00 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff0214d7348190904688376df99bce |
completed | May 9, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69feffd62fec8190a855922c8b3c57cf |
completed | May 9, 2026, 9:35 a.m. |
Created at: May 1, 2026, 1:31 a.m.