Triple
T34054201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMCS Haida |
E873310
|
entity |
| Predicate | previousHomePort |
P199198
|
FINISHED |
| Object | Halifax, Nova Scotia |
—
|
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: Halifax, Nova Scotia | Statement: [HMCS Haida, previousHomePort, Halifax, Nova Scotia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousHomePort Context triple: [HMCS Haida, previousHomePort, Halifax, Nova Scotia]
-
A.
laterHomePort
Indicates that one location served as the subsequent or later home port of a vessel or entity after an earlier home port.
-
B.
homePort
Indicates that a vessel or mobile entity is based at, registered to, or primarily operates from a particular port or harbor.
-
C.
homeportAsNOAA
Indicates that a vessel’s designated home port is assigned or recognized specifically as a NOAA (National Oceanic and Atmospheric Administration) home port.
-
D.
homeportCity
Indicates the city that serves as the primary home port or base location for a vessel or similar entity.
-
E.
previousPortOfCall
Indicates that a specified location was the last port where a vessel stopped or was registered before its current position or status.
- 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_69f349a3ec2c8190b62da76e54231a0f |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff255b84788190a94682f4efe1d0b8 |
completed | May 9, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69ff24f3ab108190bb017a656cff3d82 |
completed | May 9, 2026, 12:13 p.m. |
| PDg | Predicate description generation | batch_69ff255abca881908ef7635bd2e5af98 |
completed | May 9, 2026, 12:15 p.m. |
Created at: May 1, 2026, 1:52 a.m.