Triple
T20027395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scudetto front grille |
E495018
|
entity |
| Predicate | isBrandIdentifierFor |
P48662
|
FINISHED |
| Object | Alfa Romeo road cars |
—
|
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: Alfa Romeo road cars | Statement: [Scudetto front grille, isBrandIdentifierFor, Alfa Romeo road cars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBrandIdentifierFor Context triple: [Scudetto front grille, isBrandIdentifierFor, Alfa Romeo road cars]
-
A.
isBrand
Indicates that one entity functions as the commercial brand or label associated with another entity.
-
B.
hasBrandIdentityElement
chosen
Indicates that an entity includes or is associated with a specific component of its overall brand identity (such as a logo, color scheme, or tagline).
-
C.
usesSameBrandFamilyAs
Indicates that two entities use products or services belonging to the same overarching brand family or brand portfolio.
-
D.
hasBrandType
Indicates that an entity is associated with or categorized under a particular brand type or classification.
-
E.
supportsBrand
Indicates that one entity endorses, promotes, or is compatible with a particular brand.
- 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6628e1eec81908e4c9b2b0b68f0e4 |
completed | April 20, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69e54ce752748190a0a1ffddd0372271 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:35 p.m.