Triple
T17110772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Majestic (1890) |
E415217
|
entity |
| Predicate | blueRibandHolder |
P125977
|
FINISHED |
| Object | 1891 |
—
|
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: 1891 | Statement: [SS Majestic (1890), blueRibandHolder, 1891]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blueRibandHolder Context triple: [SS Majestic (1890), blueRibandHolder, 1891]
-
A.
wearsRibbonOf
Indicates that one entity is adorned with or has attached to it a ribbon associated with another entity.
-
B.
blueRibbonSportsLaterBecame
Indicates that one entity, originally known as Blue Ribbon Sports, subsequently changed its name or identity to become another specified entity.
-
C.
flagBearer
Indicates that one entity serves as the carrier or holder of a flag on behalf of another entity, group, or cause.
-
D.
hasInsigniaWornBy
Indicates that a particular insignia is worn by a specified entity (such as a person, group, or organization).
-
E.
qualificationBadge
Indicates that an entity has been awarded or holds a specific qualification badge signifying a certified skill, status, or achievement.
- 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dc2a7f2c81908eb19594b6accab7 |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d6b1b988190a8d6b6fe78c35e59 |
completed | April 18, 2026, 10:31 a.m. |
| PDg | Predicate description generation | batch_69e37542d060819082aa73948eb8ebd4 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:35 a.m.