Triple
T23774405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palestrina Pietà |
E587628
|
entity |
| Predicate | possiblyBy |
P153893
|
FINISHED |
| Object | Michelangelo |
—
|
NE NERFINISHED |
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: Michelangelo | Statement: [Palestrina Pietà, possiblyBy, Michelangelo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possiblyBy Context triple: [Palestrina Pietà, possiblyBy, Michelangelo]
-
A.
possibleRelative
Indicates a relationship where one entity may be related to another by family or kinship, but the exact nature of the relationship is uncertain or not fully established.
-
B.
possibleJudgment
Indicates a potential or anticipated judgment, decision, or evaluative outcome that could be made about an entity or situation.
-
C.
possiblyRuledAs
Indicates that one entity may have exercised governance or authority over another, but this ruling is uncertain or not definitively established.
-
D.
couldPass
Indicates that one entity had the ability or potential to move through, overcome, or be accepted by another entity or barrier.
-
E.
possibleResponse
Indicates that an entity is a valid or acceptable reply, answer, or reaction to another entity or situation.
- F. None of above. chosen
Provenance (4 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_69e2490d245881909028226a1393d624 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1c468fb948190baa66a4353f0ca71 |
completed | April 29, 2026, 8:42 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
| PDg | Predicate description generation | batch_69f15ed138f88190a8ae555422978908 |
completed | April 29, 2026, 1:28 a.m. |
Created at: April 17, 2026, 7:16 p.m.