Triple
T27902058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spirit of Vancouver Island |
E705660
|
entity |
| Predicate | refitLocation |
P3155
|
FINISHED |
| Object | Remontowa Shiprepair Yard, Gdańsk, Poland |
—
|
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: Remontowa Shiprepair Yard, Gdańsk, Poland | Statement: [Spirit of Vancouver Island, refitLocation, Remontowa Shiprepair Yard, Gdańsk, Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refitLocation Context triple: [Spirit of Vancouver Island, refitLocation, Remontowa Shiprepair Yard, Gdańsk, Poland]
-
A.
refit
chosen
Indicates that an existing object or structure is being modified, repaired, or equipped with new parts or features to restore or improve its function.
-
B.
rematchLocation
Indicates the place where a subsequent or repeat encounter between the same parties takes place.
-
C.
setLocation
Indicates assigning or updating the place or position where an entity is located.
-
D.
deltaLocation
Indicates a change or difference between two locations, typically specifying how one location has shifted relative to another.
-
E.
refersToLocation
Indicates that one entity designates, points to, or identifies a specific location associated with it.
- 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_69ef96b490ac8190a412d04c5d009f3e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 6:42 p.m.