Triple
T34590521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port system of Indonesia |
E888167
|
entity |
| Predicate | includesPortCategory |
P70092
|
FINISHED |
| Object | international hub port |
—
|
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: international hub port | Statement: [Port system of Indonesia, includesPortCategory, international hub port]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesPortCategory Context triple: [Port system of Indonesia, includesPortCategory, international hub port]
-
A.
includesPort
Indicates that one entity contains, encompasses, or has as part of it a specific port or set of ports.
-
B.
portCategory
Indicates the classification or type assigned to a port based on its function, usage, or characteristics.
-
C.
containsCategory
chosen
Indicates that one entity includes or encompasses a specific category as part of its classification or organizational structure.
-
D.
supportsCategory
Indicates that one entity is capable of handling, accommodating, or being compatible with a specified category.
-
E.
hasCategoryWithin
Indicates that one category is contained within or is a subcategory of another category.
- 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_69f349d3bfcc81909874c99e646fb3ea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:03 a.m.