Triple
T23086493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grecale Trofeo |
E575616
|
entity |
| Predicate | infotainmentDisplay |
P41649
|
FINISHED |
| Object | central touchscreen display |
—
|
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: central touchscreen display | Statement: [Grecale Trofeo, infotainmentDisplay, central touchscreen display]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: infotainmentDisplay Context triple: [Grecale Trofeo, infotainmentDisplay, central touchscreen display]
-
A.
displays
Indicates that one entity visually presents or shows another entity’s content or information.
-
B.
displaysFeature
chosen
Indicates that one entity presents, shows, or makes visible a particular feature or characteristic of another entity.
-
C.
displayController
Indicates a relationship where one entity manages or controls the visual output or presentation of information on a display device for another entity.
-
D.
displayConfiguration
Indicates a relationship where one entity defines or presents the arrangement, layout, or settings used to visually display another entity.
-
E.
viaStation
Indicates that a route, journey, or connection passes through or is served by a particular intermediate station.
- 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_69e245bf3e3c819086d3448720efc01b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18da652ac819085919ade6dd7bce4 |
completed | April 29, 2026, 4:48 a.m. |
| PD | Predicate disambiguation | batch_69ef89e5ce748190b2c3ac3843484127 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:57 p.m.