Triple
T29390088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SD memory card |
E745349
|
entity |
| Predicate | speedClassMarking |
P167140
|
FINISHED |
| Object | C2 |
—
|
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: C2 | Statement: [SD memory card, speedClassMarking, C2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speedClassMarking Context triple: [SD memory card, speedClassMarking, C2]
-
A.
speedClass
Indicates the categorical speed level or range assigned to an entity based on how fast it moves or operates.
-
B.
recordSpeedCategory
Indicates the classification of an entity’s speed into a predefined category (e.g., slow, normal, fast) based on its recorded speed.
-
C.
speedClassOfTrains
Indicates the classification of trains based on their operating speed or speed category.
-
D.
hasSpeedRegime
Indicates a relationship where an entity is associated with a particular speed range or operating speed condition under which it functions or is evaluated.
-
E.
homologationClass
Indicates the specific regulatory or competitive category under which something (typically a vehicle or product) has been officially approved or certified.
- 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_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_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 28, 2026, 2:41 p.m.