Triple
T2199117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford Mustang Bullitt edition |
E50446
|
entity |
| Predicate | hasPerformanceFocus |
P31
|
FINISHED |
| Object | improved handling |
—
|
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: improved handling | Statement: [Ford Mustang Bullitt edition, hasPerformanceFocus, improved handling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerformanceFocus Context triple: [Ford Mustang Bullitt edition, hasPerformanceFocus, improved handling]
-
A.
featuresPerformanceBy
Indicates a relationship where something (such as an event, work, or production) includes or showcases a performance given by a particular performer or group.
-
B.
hasPerformanceConvention
Indicates that there is an agreed-upon set of rules, norms, or standards governing how a particular performance or activity should be carried out.
-
C.
focusesOn
chosen
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
D.
hasProgrammingFocus
Indicates that something is centered on, specialized in, or primarily concerned with programming.
-
E.
hasPrimaryGoal
Indicates that an entity’s main or most important objective is the specified goal.
- 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_69a88b044ab48190add007487680f009 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abbf7b65cc8190bcc5a5c52b90f33b |
completed | March 7, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69abbda706f4819094de73e1d1d1f539 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.