Triple
T37927122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gear |
E946122
|
entity |
| Predicate | suitFeature |
P189622
|
FINISHED |
| Object | full-face helmet with visor |
—
|
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: full-face helmet with visor | Statement: [Gear, suitFeature, full-face helmet with visor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suitFeature Context triple: [Gear, suitFeature, full-face helmet with visor]
-
A.
suit
Indicates that one entity is appropriate, fitting, or satisfactory for another entity or a particular purpose or situation.
-
B.
suitType
Indicates the specific category or style of suit associated with an entity (e.g., business suit, spacesuit, wetsuit).
-
C.
suitProperties
Indicates that certain properties or characteristics are appropriate, compatible, or well-matched to a given entity or context.
-
D.
suitSystem
Indicates that one entity is compatible with, designed for, or appropriately matched to a particular system.
-
E.
featuresSuit
Indicates that one entity includes or presents a particular suit (e.g., clothing, armor, or outfit) as a notable component or attribute.
- 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_69f76ef3b7248190892fb9706423be7c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc7b6c2c88190ad4f58980834053c |
completed | May 6, 2026, 10:59 p.m. |
Created at: May 3, 2026, 4:20 p.m.