Triple
T33956291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vert Skateboarding |
E870580
|
entity |
| Predicate | typicalProtectiveGear |
P130667
|
FINISHED |
| Object | helmet |
—
|
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: helmet | Statement: [Vert Skateboarding, typicalProtectiveGear, helmet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalProtectiveGear Context triple: [Vert Skateboarding, typicalProtectiveGear, helmet]
-
A.
protectiveEquipment
Indicates that one entity serves as protective equipment used to safeguard another entity from harm or risk.
-
B.
typicalGear
chosen
Indicates that the object represents the usual or standard equipment or gear commonly associated with the subject.
-
C.
safetyEquipment
Indicates that one entity serves as safety equipment used to protect another entity from harm or danger.
-
D.
hasTypicalArmor
Indicates that an entity normally wears or is equipped with a standard or characteristic type of armor.
-
E.
typicalGuard
Indicates that an entity commonly or characteristically serves in a guarding or protective role relative to another entity or 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_69f3499c2d7481909c953a5010227725 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:49 a.m.