Triple
T16119075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spyker F8-VII |
E391084
|
entity |
| Predicate | regulatoryEra |
P80369
|
FINISHED |
| Object | 2.4-litre V8 era |
—
|
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: 2.4-litre V8 era | Statement: [Spyker F8-VII, regulatoryEra, 2.4-litre V8 era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatoryEra Context triple: [Spyker F8-VII, regulatoryEra, 2.4-litre V8 era]
-
A.
regulationEra
chosen
Indicates the historical or temporal period during which a particular regulation or regulatory framework was in effect.
-
B.
emissionsEra
Indicates the time period or era during which the emissions associated with an entity occur or are recorded.
-
C.
hasRegulationHistory
Indicates that there exists a record or sequence of regulatory actions, decisions, or statuses associated with the entity over time.
-
D.
managedEra
Indicates that one entity oversaw, directed, or was responsible for the management of a particular historical or temporal period associated with another entity.
-
E.
usedDuringEraOf
Indicates that something was in use or actively employed during the time period or historical era associated with another entity.
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2016d527c8190928e73661b18a914 |
completed | April 17, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e1828518c48190a8ef3aaa46a1f639 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5 a.m.