Triple
T7566265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hovedøya |
E178919
|
entity |
| Predicate | hasPortOfDeparture |
P46825
|
FINISHED |
| Object | Rådhusbrygge 4 |
—
|
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: Rådhusbrygge 4 | Statement: [Hovedøya, hasPortOfDeparture, Rådhusbrygge 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPortOfDeparture Context triple: [Hovedøya, hasPortOfDeparture, Rådhusbrygge 4]
-
A.
placeOfDeparture
Indicates the location from which an entity, such as a person or vehicle, begins its journey or movement.
-
B.
departsFrom
chosen
Indicates that an entity (such as a vehicle, person, or process) begins its movement, journey, or operation starting from a specified location or point of origin.
-
C.
isPortOfCallFor
Indicates that a location serves as a scheduled stop or destination for a ship, vehicle, or journey.
-
D.
placeOfArrival
Indicates the location at which an entity or person arrives at the end of a journey, movement, or transfer.
-
E.
hasPortCity
Indicates that a place or region possesses or is associated with a city that functions as its port.
- 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_69c69f2f80288190b95cceb4da92ab2b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8fde87c81909795fc713d7378ff |
completed | March 27, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69c6f4dc485c819080da13e3b7f4f08f |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:50 p.m.