Triple
T28426428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ミナミ |
E720090
|
entity |
| Predicate | 対比されるエリア |
P100119
|
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: [ミナミ, 対比されるエリア, キタ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 対比されるエリア Context triple: [ミナミ, 対比されるエリア, キタ]
-
A.
regionComparedTo
chosen
Indicates a comparative relationship between two regions, specifying how one region differs from or relates to the other along a particular dimension (e.g., size, value, or status).
-
B.
所在地エリア
Indicates the geographical area or region in which an entity is located or based.
-
C.
contrastedWithBoundary
Indicates a relationship where one entity is compared or set in opposition to a defining limit, edge, or boundary of another entity to highlight their differences.
-
D.
oftenContrastedWith
Indicates that one entity is frequently compared to another in a way that highlights their differences or opposing characteristics.
-
E.
modernAreaCorrespondsTo
Indicates that a historical or former area is associated with, or has its equivalent in, a specified modern geographic or administrative area.
- 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_69eff6f1c5088190bc24bfbf92f9c017 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 1:37 a.m.