Triple
T37759552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Empress of Canada (1948) |
E941220
|
entity |
| Predicate | fireLocation |
P189007
|
FINISHED |
| Object | Port of Miami |
—
|
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: Port of Miami | Statement: [SS Empress of Canada (1948), fireLocation, Port of Miami]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fireLocation Context triple: [SS Empress of Canada (1948), fireLocation, Port of Miami]
-
A.
fireOccurred
Indicates that a fire event took place at a specific time and/or location.
-
B.
fireBeganAt
Indicates that the event of a fire starting occurred at a specific time or location.
-
C.
fireType
Indicates that one entity has a specific classification or category related to fire (e.g., type, kind, or nature of fire).
-
D.
fireSpreadTo
Indicates that a fire originating in one location has extended and begun burning in another specified location.
-
E.
fireIncidentRelated
Indicates that there is a connection or association between a specific fire incident and another entity, event, or record.
- 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_69f76ee3251881909bb4451aad50752b |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaf48ba148190a8bdfd6846ad0540 |
completed | May 6, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbaeef9c488190babb546b962b4fb6 |
completed | May 6, 2026, 9:13 p.m. |
Created at: May 3, 2026, 4:19 p.m.