Triple
T20027412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scudetto front grille |
E495018
|
entity |
| Predicate | isKeyDifferentiatorFrom |
P14118
|
FINISHED |
| Object | other car manufacturers’ front grilles |
—
|
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: other car manufacturers’ front grilles | Statement: [Scudetto front grille, isKeyDifferentiatorFrom, other car manufacturers’ front grilles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isKeyDifferentiatorFrom Context triple: [Scudetto front grille, isKeyDifferentiatorFrom, other car manufacturers’ front grilles]
-
A.
isDistinguishedBy
chosen
Indicates that one entity is characterized or set apart from others by a particular feature, quality, or attribute.
-
B.
isKeyDependent
Indicates that one entity’s existence, validity, or identification depends on another entity’s key or primary identifier.
-
C.
isDistinctFrom
Indicates that two entities are not identical and can be clearly distinguished from one another.
-
D.
hasKeyType
Indicates that an entity possesses or is associated with a specific category or type of key.
-
E.
keyType
Indicates the classification or category of a key in relation to how it is used or defined within a system or context.
- 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.