Triple
T27902056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spirit of Vancouver Island |
E705660
|
entity |
| Predicate | underwentRefit |
P3155
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Spirit of Vancouver Island, underwentRefit, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underwentRefit Context triple: [Spirit of Vancouver Island, underwentRefit, 2018]
-
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.
armamentAfterRefit
Indicates that the armament of an entity reflects its configuration after undergoing a refit or upgrade.
-
C.
notableShipRepaired
Indicates that an entity is recognized for having repaired a ship of particular significance or notability.
-
D.
typeAfterRefit
Indicates that an entity’s type or classification after undergoing a refit or modification is the specified value.
-
E.
underwentUpgrade
Indicates that an entity has experienced an improvement or enhancement process that changed it to a newer or more advanced state.
- 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_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 27, 2026, 6:42 p.m.