Triple
T169613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kobe |
E3089
|
entity |
| Predicate | portStatus |
P1763
|
FINISHED |
| Object | one of Japan’s major container ports |
—
|
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: one of Japan’s major container ports | Statement: [Kobe, portStatus, one of Japan’s major container ports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portStatus Context triple: [Kobe, portStatus, one of Japan’s major container ports]
-
A.
port
chosen
Indicates a relationship where one entity serves as a harbor, access point, or interface through which another entity can enter, exit, or connect.
-
B.
portNumber
Indicates the specific communication port assigned to a network connection, service, or endpoint.
-
C.
deFactoStatus
Indicates that one entity holds a role, position, or status in practice or by custom, even if it is not formally or legally recognized.
-
D.
hostState
Indicates a relationship where one entity serves as the host or governing state for another entity, within whose jurisdiction, territory, or authority that other entity operates or resides.
-
E.
status
Indicates the current condition, state, or standing of an entity within a given context.
- 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_69a2524ce1e48190ab066bf72859f474 |
completed | Feb. 28, 2026, 2:26 a.m. |
| NER | Named-entity recognition | batch_69a258b6f4f88190b1264bbbeb19a29e |
completed | Feb. 28, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69a25665f5b8819096ca3e084faf976e |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:34 a.m.