Triple
T36699674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Empress of Canada (2036) |
E906189
|
entity |
| Predicate | hasPlannedSecondaryFunction |
P78228
|
FINISHED |
| Object | leisure cruising |
—
|
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: leisure cruising | Statement: [SS Empress of Canada (2036), hasPlannedSecondaryFunction, leisure cruising]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlannedSecondaryFunction Context triple: [SS Empress of Canada (2036), hasPlannedSecondaryFunction, leisure cruising]
-
A.
hasPlannedPrimaryFunction
Indicates that an entity is intended or designed to perform a specified main function or role.
-
B.
hasSecondary
Indicates that an entity is associated with an additional or subordinate counterpart beyond its primary one.
-
C.
hasSecondaryUsage
chosen
Indicates that an entity is associated with an additional, non-primary function or purpose beyond its main intended use.
-
D.
hasPlanningFunction
Indicates that an entity is responsible for or involved in planning, organizing, or determining future actions or strategies.
-
E.
hasSecondaryComponent
Indicates that an entity includes or is associated with an additional, subordinate component beyond its primary one.
- 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_69f76e7195c48190b5580c9cfb01e95f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe031bc6208190860099aef72d8dcb |
completed | May 8, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69fe014c8b388190b5d4e0cb95ee2be5 |
completed | May 8, 2026, 3:29 p.m. |
Created at: May 3, 2026, 4:12 p.m.