Triple
T36078203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angel with the Whips |
E1043556
|
entity |
| Predicate | invitesResponse |
P10012
|
FINISHED |
| Object | meditation on Christ’s Passion |
—
|
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: meditation on Christ’s Passion | Statement: [Angel with the Whips, invitesResponse, meditation on Christ’s Passion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: invitesResponse Context triple: [Angel with the Whips, invitesResponse, meditation on Christ’s Passion]
-
A.
invitesResponseOf
chosen
Indicates that one entity’s action, message, or state prompts, elicits, or calls for a response from another entity.
-
B.
invitesToLocation
Indicates that one entity extends an invitation to another entity to go to or be present at a specific location.
-
C.
invitesParticipationOf
Indicates that one entity actively requests or encourages another entity to take part in an activity, event, or process.
-
D.
isInvited
Indicates that one entity has extended an invitation to another entity to participate in or attend something.
-
E.
invitationBy
Indicates that one entity is the inviter or originator of an invitation extended to another entity.
- 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_69f76e3154908190a6f702671c2bea08 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b2c771108190adeec151daad5dab |
completed | May 3, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.