Triple
T4821408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maserati Quattroporte |
E107717
|
entity |
| Predicate | firstGenerationLaunchYear |
P25152
|
FINISHED |
| Object | 1963 |
—
|
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: 1963 | Statement: [Maserati Quattroporte, firstGenerationLaunchYear, 1963]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstGenerationLaunchYear Context triple: [Maserati Quattroporte, firstGenerationLaunchYear, 1963]
-
A.
firstGenerationReleaseDate
Indicates the calendar date on which the first generation or initial version of something was officially released.
-
B.
firstGenerationStart
chosen
Indicates the point in time or event at which the first generation in a sequence, lineage, or series begins.
-
C.
firstProductionYear
Indicates the year in which something (such as a product, work, or item) was first produced.
-
D.
firstRunningYear
Indicates the year in which something (such as an event, service, or operation) first began running or was initially active.
-
E.
wasFirstBuiltInYear
Indicates that the initial construction of an entity was completed in a specified year.
- 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_69bd43f9efa081908314cb3e94fa1695 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1fe130819087ae01309f96a0c8 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:24 p.m.