Triple
T36510252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Empress of Canada (1974) |
E899879
|
entity |
| Predicate | enteredCarnivalServiceAsMardiGras |
P182439
|
FINISHED |
| Object | 1972 |
—
|
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: 1972 | Statement: [SS Empress of Canada (1974), enteredCarnivalServiceAsMardiGras, 1972]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredCarnivalServiceAsMardiGras Context triple: [SS Empress of Canada (1974), enteredCarnivalServiceAsMardiGras, 1972]
-
A.
enteredCarnivalServiceYear
chosen
Indicates the year in which an entity began its service or operational role within a carnival.
-
B.
carnivalFrequency
Indicates how often a carnival event occurs within a given time period.
-
C.
carnivalRecognizedAs
Indicates that one carnival is acknowledged, designated, or officially regarded as a particular type, status, or identity.
-
D.
Águilas Carnival
Indicates a relationship where an event, celebration, or festivity is specifically identified as the Águilas Carnival.
-
E.
CrownParty
Indicates that a party is formally recognized as the reigning monarch or sovereign authority in a legal or ceremonial context.
- 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_69f76e5dada881909da2d34bc7a9202a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.