Triple
T16730793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hythe, Hampshire |
E406584
|
entity |
| Predicate | pierType |
P81727
|
FINISHED |
| Object | passenger pier |
—
|
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: passenger pier | Statement: [Hythe, Hampshire, pierType, passenger pier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pierType Context triple: [Hythe, Hampshire, pierType, passenger pier]
-
A.
hasPier
Indicates that a location or structure possesses or includes a pier as part of its features.
-
B.
hasPiersOn
Indicates that one structure or location is supported or extended by piers that are physically situated on another structure or surface.
-
C.
berthType
Indicates the specific kind or category of berth associated with an entity, such as the type of sleeping or docking space provided.
-
D.
isNumberedPierOf
Indicates that one entity is a specific numbered pier belonging to or associated with another entity (such as a port, harbor, or waterfront facility).
-
E.
specializesPierAIn
chosen
Indicates that one entity (typically a pier or terminal) is specifically designated or adapted for a particular type of use, service, or function.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3874bd7648190a6a7d173d4b497a7 |
completed | April 18, 2026, 1:29 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.