Triple
T33807641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Need for Speed: Underground 2 |
E866436
|
entity |
| Predicate | notableCarBrands |
P51141
|
FINISHED |
| Object | Nissan |
E21556
|
NE 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: Nissan | Statement: [Need for Speed: Underground 2, notableCarBrands, Nissan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCarBrands Context triple: [Need for Speed: Underground 2, notableCarBrands, Nissan]
-
A.
notableCar
Indicates that the subject is a car recognized for its significance, prominence, or special interest (e.g., historically, culturally, or technically).
-
B.
notableModelFamily
Indicates that one entity is a prominent or widely recognized model family associated with, produced by, or otherwise notably linked to another entity.
-
C.
notableManufacturer
chosen
Indicates that an entity is a well-known or prominent producer or maker of another entity.
-
D.
notableTrainBrand
Indicates that an entity is a well-known or significant brand associated with trains or railway services.
-
E.
carManufacturer
Indicates that one entity is the company that produces or manufactures the car represented by the other entity.
- F. None of above.
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_69f3499057fc81909d862b1309a3bd71 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36760934408190915f213ef79baa53 |
completed | June 20, 2026, 11:14 a.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:46 a.m.