Triple
T3088367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rock 'n' Roller Coaster Starring Aerosmith |
E64427
|
entity |
| Predicate | safetyRestraintType |
P22102
|
FINISHED |
| Object | over-the-shoulder harness |
—
|
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: over-the-shoulder harness | Statement: [Rock 'n' Roller Coaster Starring Aerosmith, safetyRestraintType, over-the-shoulder harness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: safetyRestraintType Context triple: [Rock 'n' Roller Coaster Starring Aerosmith, safetyRestraintType, over-the-shoulder harness]
-
A.
restraintType
chosen
Indicates the specific kind or method of restraint applied in a given situation or relationship.
-
B.
usesBeltSystem
Indicates that a subject employs a structured belt-ranking system (e.g., colored belts) to denote levels of skill, progress, or status.
-
C.
sealType
Indicates the specific kind or category of seal associated with an entity or connection.
-
D.
hasArmrestType
Indicates the specific style or configuration of armrests associated with an item.
-
E.
protectionType
Indicates the kind or method of protection that is applied to or associated with an 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_69ad857c97d88190b26f9b1c90839c77 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada209fd24819088d887de0a4158f4 |
completed | March 8, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69ad9ded78f881908be6fc0fb7c35764 |
completed | March 8, 2026, 4:03 p.m. |
Created at: March 8, 2026, 3:03 p.m.