Triple
T6874930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Authority of New South Wales |
E158648
|
entity |
| Predicate | service area |
P82
|
FINISHED |
| Object | commercial shipping |
—
|
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: commercial shipping | Statement: [Port Authority of New South Wales, service area, commercial shipping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: service area Context triple: [Port Authority of New South Wales, service area, commercial shipping]
-
A.
areaServed
chosen
Indicates the geographic region or jurisdiction within which a service, organization, or activity is provided or applicable.
-
B.
areaServedType
Indicates the type or category of area that is served by an entity or service.
-
C.
serviceAreaCharacteristic
Indicates a relationship where a service area is associated with a specific attribute or feature that characterizes it.
-
D.
hasServiceAreas
Indicates that an entity provides services within, or is operational across, specific geographic or functional areas.
-
E.
sectorServed
Indicates the industry or economic sector that an entity primarily serves or targets with its activities, products, or services.
- 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_69c68832af1481908ce356e133ebaebe |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d8c9e7b481909079b0f1fb1bc217 |
completed | March 27, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b363dc8190a7225b540ab2bc40 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:22 p.m.