Triple
T28874489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TPP |
E732229
|
entity |
| Predicate | portCodeFor |
P24997
|
FINISHED |
| Object | Port of Tanjung Pelepas |
—
|
NE NERFINISHED |
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: Port of Tanjung Pelepas | Statement: [TPP, portCodeFor, Port of Tanjung Pelepas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portCodeFor Context triple: [TPP, portCodeFor, Port of Tanjung Pelepas]
-
A.
portCodeLOCODE
Indicates that a port is identified by a specific LOCODE (Location Code) value.
-
B.
hasPortCode
chosen
Indicates that an entity (such as a port or terminal) is associated with a specific standardized port code identifier.
-
C.
planeCode
Indicates that an entity is associated with a specific identifying code assigned to a plane.
-
D.
isPortOf
Indicates that one location or facility serves as a port or harbor for another place, entity, or transportation route.
-
E.
airportCodeContext
Indicates that an airport code is being used or interpreted within a specific contextual framework (such as a region, system, or standard) that defines its meaning.
- 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65a4a48888190b3c1bc721712ae71 |
completed | May 2, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 7:36 a.m.