Triple
T10325060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SCCA Trans-Am Series |
E242740
|
entity |
| Predicate | historicClass |
P9609
|
FINISHED |
| Object | over 2.0 liter 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: over 2.0 liter class | Statement: [SCCA Trans-Am Series, historicClass, over 2.0 liter class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicClass Context triple: [SCCA Trans-Am Series, historicClass, over 2.0 liter class]
-
A.
historicFor
Indicates that something holds historical significance or importance specifically in relation to another entity.
-
B.
historicActivity
Indicates that an entity engaged in an activity or event of historical significance in the past.
-
C.
historicalCategory
chosen
Indicates that an entity is classified within a particular historical grouping, period, or type based on its time-related characteristics or context.
-
D.
historical
Indicates that the subject has existed, occurred, or been relevant in the past rather than in the present or future.
-
E.
historicalType
Indicates that one entity classifies or characterizes another in terms of its role, status, or category within a historical 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f64a648190a79980d647898eb0 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:51 a.m.