Triple
T1244295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Boston |
E26728
|
entity |
| Predicate | hasPilotage |
P25928
|
FINISHED |
| Object | compulsory pilotage area |
—
|
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: compulsory pilotage area | Statement: [Port of Boston, hasPilotage, compulsory pilotage area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPilotage Context triple: [Port of Boston, hasPilotage, compulsory pilotage area]
-
A.
hasPier
Indicates that a location or structure possesses or includes a pier as part of its features.
-
B.
hasNavigationAid
Indicates that one entity provides or is equipped with a navigation aid used to assist in determining position or direction.
-
C.
pilotDirector
Indicates that one entity serves as the director of the pilot episode or initial installment of another entity (such as a series or project).
-
D.
hasNave
Indicates that one entity (typically a building or structure) possesses or includes a nave as a distinct architectural part.
-
E.
hasHarbor
Indicates that a place possesses or contains a harbor for docking or sheltering vessels.
- 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_69a4948689d08190b3a4a3f388c02148 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bf636e208190a4d56806db61916c |
completed | March 1, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69a4bb696a38819095845c84f0241287 |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bce611ec819092cb13d354d0903e |
completed | March 1, 2026, 10:25 p.m. |
Created at: March 1, 2026, 7:47 p.m.