Triple
T19946936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maserati Levante |
E479444
|
entity |
| Predicate | introducedAsFirst |
P137957
|
FINISHED |
| Object | Maserati’s first SUV model |
—
|
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: Maserati’s first SUV model | Statement: [Maserati Levante, introducedAsFirst, Maserati’s first SUV model]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedAsFirst Context triple: [Maserati Levante, introducedAsFirst, Maserati’s first SUV model]
-
A.
firstPresentedFor
Indicates that one entity was initially introduced, submitted, or shown to another entity at a particular time or context.
-
B.
firstAppeared
Indicates the earliest known time or context in which an entity was introduced, observed, or came into existence.
-
C.
firstIntroductionDate
Indicates the date on which an entity was first introduced or presented for the first time.
-
D.
firstUsedAs
Indicates that one entity was the earliest or original thing in which another entity was used or applied.
-
E.
firstReleasedAs
Indicates the original title or form under which an entity (such as a work, product, or version) was initially released before any later re-releases, renamings, or editions.
- 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a68a32c8190ac9601db98594465 |
completed | April 20, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69e537f47c508190853c4e009c6b5566 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c42c688190a22f4d31ec692377 |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:54 p.m.