Triple
T29390085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SD memory card |
E745349
|
entity |
| Predicate | speedClassSystem |
P9902
|
FINISHED |
| Object | Speed Class |
—
|
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: Speed Class | Statement: [SD memory card, speedClassSystem, Speed Class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speedClassSystem Context triple: [SD memory card, speedClassSystem, Speed Class]
-
A.
speedClass
chosen
Indicates the categorical speed level or range assigned to an entity based on how fast it moves or operates.
-
B.
sportClassificationSystem
Indicates a system or scheme used to categorize and organize sports into defined types, groups, or classes based on shared characteristics or rules.
-
C.
raceGradeSystem
Indicates a grading or classification relationship that assigns a performance or quality level to a race or racing event.
-
D.
recordSpeedCategory
Indicates the classification of an entity’s speed into a predefined category (e.g., slow, normal, fast) based on its recorded speed.
-
E.
speedClassOfTrains
Indicates the classification of trains based on their operating speed or speed category.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f669d648488190b7d3060432eb0eeb |
completed | May 2, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:41 p.m.