Triple
T28200820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chita Peninsula |
E716877
|
entity |
| Predicate | oppositeAcrossBayFrom |
P44148
|
FINISHED |
| Object | Mie Prefecture across Ise Bay |
—
|
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: Mie Prefecture across Ise Bay | Statement: [Chita Peninsula, oppositeAcrossBayFrom, Mie Prefecture across Ise Bay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oppositeAcrossBayFrom Context triple: [Chita Peninsula, oppositeAcrossBayFrom, Mie Prefecture across Ise Bay]
-
A.
locatedAcrossRiverFrom
Indicates that one entity is situated on the opposite side of a river relative to another entity.
-
B.
locatedInBayOf
Indicates that something is situated within or directly on a specific bay.
-
C.
oppositeShoreFrom
chosen
Indicates that two locations are situated on facing sides of the same body of water or shoreline, directly across from each other.
-
D.
isCentralWaterfrontOf
Indicates that one location serves as the primary waterfront area or main waterside district of another place.
-
E.
bayOf
Indicates that one location is a bay that forms an inlet or coastal indentation associated with another geographic entity, such as a sea, ocean, or coastline.
- 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_69efd6b826908190857e6e7dad74ed93 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 27, 2026, 10:31 p.m.