Triple
T2300245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford S650 platform |
E51712
|
entity |
| Predicate | engineeringFocus |
P15961
|
FINISHED |
| Object | performance |
—
|
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: performance | Statement: [Ford S650 platform, engineeringFocus, performance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineeringFocus Context triple: [Ford S650 platform, engineeringFocus, performance]
-
A.
engineeringFeature
Indicates that one entity serves as an engineering-related feature, component, or characteristic of another entity within a technical or designed system.
-
B.
hasEngineeringSignificance
chosen
Indicates that something holds notable importance, impact, or relevance within an engineering context or for engineering activities.
-
C.
programmingFocus
Indicates a relationship where an entity’s primary attention, effort, or specialization is directed toward a particular area or aspect of programming.
-
D.
programFocus
Indicates that an educational or training program is primarily oriented around or concentrated on a particular subject, theme, or objective.
-
E.
laterEngineer
Indicates that one entity becomes an engineer at a later time than another entity.
- 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_69a88b0a9f248190bcff941463d8f65a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abcbabf01081908db3b42bc7c60444 |
completed | March 7, 2026, 6:54 a.m. |
| PD | Predicate disambiguation | batch_69abc58ad33c8190b8d68af41b6f5e07 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.