Triple
T612273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyde Street Pier |
E12123
|
entity |
| Predicate | eraOfMajorUseAsFerryTerminal |
P17099
|
FINISHED |
| Object | early 20th century |
—
|
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: early 20th century | Statement: [Hyde Street Pier, eraOfMajorUseAsFerryTerminal, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfMajorUseAsFerryTerminal Context triple: [Hyde Street Pier, eraOfMajorUseAsFerryTerminal, early 20th century]
-
A.
hasFerryPort
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.
linkedByFerryTo
Indicates that one place is connected to another by a ferry route that enables transport between them.
-
D.
isPortOfCallFor
Indicates that a location serves as a scheduled stop or destination for a ship, vehicle, or journey.
-
E.
hasPassengerTerminal
Indicates that one entity possesses or is equipped with a passenger terminal used for boarding, alighting, or handling passengers.
- F. None of above. chosen
Provenance (4 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_69a493309df48190a327f748e88049a6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49e07739481909930a6577c081b9e |
completed | March 1, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69a49cfa7b4481909bec7a5fd3e98c65 |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49def31ec81909dc53e70f4a36eda |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:35 p.m.