Triple
T27678481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spirit of British Columbia |
E697843
|
entity |
| Predicate | conversionYard |
P168953
|
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 British Columbia, conversionYard, Remontowa Shiprepair Yard, Gdańsk, Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conversionYard Context triple: [Spirit of British Columbia, conversionYard, Remontowa Shiprepair Yard, Gdańsk, Poland]
-
A.
hasYard
Indicates that one entity possesses or includes a yard as part of its property or premises.
-
B.
lengthInSmoots
Indicates that one entity has a length measured in Smoots, using the other entity as the numeric value of that length.
-
C.
distanceInFurlongs
Indicates the physical separation between two entities measured in units of furlongs.
-
D.
conversionUse
Indicates that one entity is used as a means, method, or context for converting another entity from one form, state, or representation to another.
-
E.
yardsPerCarry
Indicates the average number of yards gained per rushing attempt in a running play.
- 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_69ef590d458c81909583290c3cd0478b |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f67866e9248190b7ba218f9ca2ae8d |
completed | May 2, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676c35f3481909b9ba18a5662d6ce |
completed | May 2, 2026, 10:12 p.m. |
Created at: April 27, 2026, 2:45 p.m.