Triple
T23440223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pictou, Nova Scotia |
E565375
|
entity |
| Predicate | hasReplicaShip |
P152287
|
FINISHED |
| Object | Ship Hector replica |
—
|
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: Ship Hector replica | Statement: [Pictou, Nova Scotia, hasReplicaShip, Ship Hector replica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReplicaShip Context triple: [Pictou, Nova Scotia, hasReplicaShip, Ship Hector replica]
-
A.
hasShip
Indicates that one entity possesses, owns, or is equipped with a ship.
-
B.
hasShipLock
Indicates that one entity possesses or is equipped with a ship lock used to control water levels for vessel passage.
-
C.
hasShipRole
Indicates that an entity holds or is assigned a specific role or function on a ship.
-
D.
hasShipPrefix
Indicates that a ship is associated with or identified by a specific prefix in its name or designation.
-
E.
hasShipName
Indicates that an entity (such as a vessel or record) is associated with a specific ship name.
- 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_69e24584f9488190bb32730bd2ce023e |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a5df28288190936f16b017a20bc0 |
completed | April 29, 2026, 6:31 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:50 p.m.