Triple
T23200144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aichi, Japan |
E579983
|
entity |
| Predicate | portRole |
P130959
|
FINISHED |
| Object | major export hub for automobiles |
—
|
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: major export hub for automobiles | Statement: [Aichi, Japan, portRole, major export hub for automobiles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portRole Context triple: [Aichi, Japan, portRole, major export hub for automobiles]
-
A.
hasPortRole
chosen
Indicates that an entity participates in a port with a specified functional or operational role.
-
B.
portLocation
Indicates that a port is geographically situated at or associated with a specific location.
-
C.
port
Indicates a relationship where one entity serves as a harbor, access point, or interface through which another entity can enter, exit, or connect.
-
D.
portConfiguration
Indicates how ports are arranged, assigned, or set up for use within a system or device.
-
E.
portSystem
Indicates that one system serves as a port or interface through which another system connects, communicates, or transfers data or resources.
- 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_69e24600eed08190bd7e5295653a1503 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f19078f28c8190973f1bd6f2bceb5a |
completed | April 29, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:06 p.m.