Triple
T8078658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pirelli |
E188558
|
entity |
| Predicate | PirelliCalendarKnownFor |
P15030
|
FINISHED |
| Object | artistic photography |
—
|
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: artistic photography | Statement: [Pirelli, PirelliCalendarKnownFor, artistic photography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PirelliCalendarKnownFor Context triple: [Pirelli, PirelliCalendarKnownFor, artistic photography]
-
A.
reconocidaPor
Indicates that an entity is recognized, acknowledged, or honored by another entity.
-
B.
inscriptionFamousFor
Indicates that an inscription is widely recognized or notable specifically because of the referenced feature, event, content, or characteristic.
-
C.
refersToPersonKnownFor
Indicates that one entity makes reference to a person who is notable or recognized for some specific role, achievement, or characteristic.
-
D.
organFamousFor
Indicates that an organ is widely recognized or notable for a particular characteristic, function, or association.
-
E.
alsoKnownFor
chosen
Indicates that an entity is additionally recognized or noted for another work, role, achievement, or characteristic beyond its primary association.
- 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_69ca82b50c708190863f661d438e68df |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb40a2b64c8190ae2b3414b4f840e4 |
completed | March 31, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69cb049f1614819087360d1a4c6f0faa |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:28 p.m.