Triple
T21691719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ligurio |
E535385
|
entity |
| Predicate | goalHeSupports |
P39887
|
FINISHED |
| Object | Callimaco’s seduction of Lucrezia |
—
|
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: Callimaco’s seduction of Lucrezia | Statement: [Ligurio, goalHeSupports, Callimaco’s seduction of Lucrezia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalHeSupports Context triple: [Ligurio, goalHeSupports, Callimaco’s seduction of Lucrezia]
-
A.
goalIn
Indicates that one entity’s objective, aim, or intended outcome is located within, directed toward, or achieved inside another entity or context.
-
B.
goalsFor
Indicates the number of goals scored by one participant or team in favor of a particular side or match context.
-
C.
supportGoal
chosen
Indicates that one entity actively helps, promotes, or contributes to the achievement of another entity’s goal.
-
D.
goalType
Indicates the specific category or nature of a goal associated with an entity or action.
-
E.
goals
Indicates that an entity has objectives, targets, or desired outcomes it aims to achieve.
- 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_69e0c46a6ee481908836e1420fb78c9b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef96d0d4048190abfc3e3e06c51b8d |
completed | April 27, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69e6969113cc8190ab69855ef5667e4b |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:45 p.m.