Triple
T33767977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Need for Speed: Underground |
E865289
|
entity |
| Predicate | carBrandFeatured |
P58194
|
FINISHED |
| Object | Honda |
—
|
NE NERFINISHED |
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: Honda | Statement: [Need for Speed: Underground, carBrandFeatured, Honda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carBrandFeatured Context triple: [Need for Speed: Underground, carBrandFeatured, Honda]
-
A.
fieldedCarBrand
chosen
Indicates that a particular car brand has been entered, deployed, or represented (e.g., in a race, event, or lineup) by some agent or organization.
-
B.
carManufacturer
Indicates that one entity is the company that produces or manufactures the car represented by the other entity.
-
C.
vehicleBrandAssociated
Indicates that there is an association or linkage between a vehicle and a particular brand.
-
D.
carModel
Indicates the specific model designation of a car within a particular make or brand.
-
E.
notableCar
Indicates that the subject is a car recognized for its significance, prominence, or special interest (e.g., historically, culturally, or technically).
- 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_69f3498d3b748190aa3c4006c1f32f38 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:45 a.m.