Triple
T29050076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Charlotte City |
E735241
|
entity |
| Predicate | nearestMajorCityByFerry |
P115092
|
FINISHED |
| Object | Prince Rupert |
—
|
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: Prince Rupert | Statement: [Queen Charlotte City, nearestMajorCityByFerry, Prince Rupert]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestMajorCityByFerry Context triple: [Queen Charlotte City, nearestMajorCityByFerry, Prince Rupert]
-
A.
hasNearbyFerryPort
Indicates that one location is situated close enough to another location that serves as a ferry port to be considered nearby.
-
B.
nearestMajorCity
Indicates that one city is the closest significant urban center to another location or city compared to all other major cities.
-
C.
nearbyCityOrPort
Indicates that one location is geographically close to a city or port, typically within a short travel distance.
-
D.
nearestCityAcrossWater
chosen
Indicates that one city is the closest city to another city when considering only routes or separation across a body of water.
-
E.
hasFerryPort
Indicates that a place serves as a location where ferries regularly dock to load and unload passengers or cargo.
- 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 28, 2026, 10:07 a.m.