Triple
T34176127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 大阪港咲洲トンネル |
E876675
|
entity |
| Predicate | 通行形態 |
P10712
|
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.
crossingType
chosen
Indicates the specific kind or category of crossing (e.g., how or where one thing passes over, through, or across another).
-
B.
rightOfWayUsedFor
Indicates that a particular right of way is utilized for a specific purpose, activity, or type of use.
-
C.
hasWalkwayShape
Indicates that a walkway possesses a particular geometric or structural shape or configuration.
-
D.
crossingStyle
Indicates the manner or method by which one entity crosses or traverses another (such as a boundary, path, or medium).
-
E.
transportModeAccess
Indicates that one entity has the ability or permission to use, reach, or be served by a particular mode of transportation.
- 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_69f349ad97ac8190bf1f17417c970e64 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fe9fc488190b55b7cf618473fc6 |
completed | May 3, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:54 a.m.