Triple
T36857195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wickham, Western Australia |
E910828
|
entity |
| Predicate | hasPortFacilitiesAt |
P199647
|
FINISHED |
| Object | Cape Lambert |
—
|
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: Cape Lambert | Statement: [Wickham, Western Australia, hasPortFacilitiesAt, Cape Lambert]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPortFacilitiesAt Context triple: [Wickham, Western Australia, hasPortFacilitiesAt, Cape Lambert]
-
A.
permanentPortFacilities
Indicates that an entity has fixed, long-term port infrastructure used for maritime operations, such as docks, piers, or terminals that are not temporary or mobile.
-
B.
hasFerryPort
Indicates that a place serves as a location where ferries regularly dock to load and unload passengers or cargo.
-
C.
hasBerths
Indicates that one entity provides or contains sleeping or docking berths for another entity.
-
D.
connectsToPortFacilitiesIn
chosen
Indicates that an entity has a connection or access route to port facilities located within a specified place or region.
-
E.
isPortOf
Indicates that one location or facility serves as a port or harbor for another place, entity, or transportation route.
- 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_69f76e8033d48190a59274f86f13be48 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff9e91bba08190af04b31ad815b13a |
completed | May 9, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69ff9e00e4808190bde8f07e6519a72c |
completed | May 9, 2026, 8:50 p.m. |
Created at: May 3, 2026, 4:13 p.m.