Triple
T3622444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annie Savoy |
E76757
|
entity |
| Predicate | annualPractice |
P49600
|
FINISHED |
| Object | chooses one player each season as lover and protégé |
—
|
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: chooses one player each season as lover and protégé | Statement: [Annie Savoy, annualPractice, chooses one player each season as lover and protégé]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: annualPractice Context triple: [Annie Savoy, annualPractice, chooses one player each season as lover and protégé]
-
A.
annualFrom
Indicates that something recurs or is calculated on a yearly basis starting from a specified point in time.
-
B.
isAnnual
Indicates that something occurs, is scheduled, or is valid once every year.
-
C.
approvedPractice
Indicates that a particular practice, method, or procedure has been formally reviewed and granted official approval for use or adoption.
-
D.
annualVisitation
Indicates a recurring visit or attendance that takes place once every year between the related entities.
-
E.
annualEvent
Indicates that an event occurs once every year on a recurring basis.
- 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_69ad85dae2fc81908d1ceadbc6af0089 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc2bb12cc8190bd67597cf3b66a3a |
completed | March 8, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69adb8410a5881909c94818d7060b2b0 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb902e61c81908f10494f828e260f |
completed | March 8, 2026, 5:59 p.m. |
Created at: March 8, 2026, 3:23 p.m.