Triple
T38041898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Empress of Canada (2006) |
E949505
|
entity |
| Predicate | hasMultipleOperators |
P181232
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [SS Empress of Canada (2006), hasMultipleOperators, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMultipleOperators Context triple: [SS Empress of Canada (2006), hasMultipleOperators, true]
-
A.
hasAdditionalOperator
chosen
Indicates that an entity is associated with one or more supplementary operators beyond its primary or default operator.
-
B.
hasBasedOperators
Indicates that something is defined, constructed, or operates using a specified set of base operators.
-
C.
hasMajorOperator
Indicates that an entity is primarily operated, managed, or run by a specified main operator or organization.
-
D.
hasComplementaryOperator
Indicates that one operator is associated with another operator that performs a complementary or inverse function to it.
-
E.
hasMultiple
Indicates that an entity is associated with more than one instance or occurrence of another related entity.
- 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_69f76eff0bb0819084bc4e63997bd039 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69feced53a7c819098ec474fb7d514b0 |
completed | May 9, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69fecd9cd5288190aac8b4e04a7ee78e |
completed | May 9, 2026, 6:01 a.m. |
Created at: May 3, 2026, 4:20 p.m.