Triple
T25780314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medici Venus |
E649268
|
entity |
| Predicate | wasHighlyPraisedBy |
P11240
|
FINISHED |
| Object | Renaissance artists |
—
|
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: Renaissance artists | Statement: [Medici Venus, wasHighlyPraisedBy, Renaissance artists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasHighlyPraisedBy Context triple: [Medici Venus, wasHighlyPraisedBy, Renaissance artists]
-
A.
notablePraise
chosen
Indicates that one entity has given significant or distinguished praise or commendation to another entity.
-
B.
acclaimedFor
Indicates that an entity receives widespread praise or recognition specifically for another entity, such as a work, achievement, or contribution.
-
C.
isHighlyPrized
Indicates that something is regarded with exceptional value, admiration, or importance, often being especially sought after or cherished.
-
D.
hasHighRatingOn
Indicates that one entity is evaluated or reviewed on another entity’s platform or system with a rating that meets or exceeds a defined high threshold.
-
E.
hasReceivedCriticalAcclaim
Indicates that the subject has been widely praised or positively recognized by critics or expert reviewers.
- 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_69e7ab333b508190b6d708d8d9a328ed |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fe6072588190a6a6703251ec02bf |
completed | May 2, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 5:38 a.m.