Triple
T34525977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bunbury Port Authority |
E886398
|
entity |
| Predicate | portManaged |
P70648
|
FINISHED |
| Object | Port of Bunbury |
—
|
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 Bunbury | Statement: [Bunbury Port Authority, portManaged, Port of Bunbury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portManaged Context triple: [Bunbury Port Authority, portManaged, Port of Bunbury]
-
A.
portManagedBy
chosen
Indicates that the operation, administration, or control of a port is carried out by a specified managing entity.
-
B.
portSystem
Indicates that one system serves as a port or interface through which another system connects, communicates, or transfers data or resources.
-
C.
portActivity
Indicates the level or type of operational activity occurring at a port, such as ship movements, cargo handling, or related maritime operations.
-
D.
portConfiguration
Indicates how ports are arranged, assigned, or set up for use within a system or device.
-
E.
portHandled
Indicates that a specific port or harbor has been managed, processed, or serviced by a particular agent or system.
- 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_69f349cd7c148190aa99192b126d1527 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71fbb38a881908c41f1d8c675fa57 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:02 a.m.