Triple
T30441408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clason Point |
E774453
|
entity |
| Predicate | hasFerryLanding |
P15716
|
FINISHED |
| Object | Clason Point Park ferry landing |
—
|
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: Clason Point Park ferry landing | Statement: [Clason Point, hasFerryLanding, Clason Point Park ferry landing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFerryLanding Context triple: [Clason Point, hasFerryLanding, Clason Point Park ferry landing]
-
A.
hasFerryPort
chosen
Indicates that a place serves as a location where ferries regularly dock to load and unload passengers or cargo.
-
B.
hasFerryService
Indicates that there is an operational ferry connection or transport service available between the related locations or entities.
-
C.
hasFerryComponent
Indicates that something includes or is associated with a ferry-related part, feature, or segment within its structure or operation.
-
D.
hasNearbyFerryPort
Indicates that one location is situated close enough to another location that serves as a ferry port to be considered nearby.
-
E.
hasFerryType
Indicates that an entity (such as a ferry route or service) is associated with a specific type or category of ferry.
- 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_69f22493ef9c8190ae8c2afcb7f994c8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 29, 2026, 8:08 p.m.