Triple
T11476520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robin van Persie |
E272036
|
entity |
| Predicate | returnedToClub |
P40088
|
FINISHED |
| Object | Feyenoord in 2018 |
—
|
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: Feyenoord in 2018 | Statement: [Robin van Persie, returnedToClub, Feyenoord in 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnedToClub Context triple: [Robin van Persie, returnedToClub, Feyenoord in 2018]
-
A.
returnedToTeam
chosen
Indicates that an individual who was previously away has come back to rejoin the same team.
-
B.
returnedToTour
Indicates that an entity resumed or went back to participating in a tour after having left or paused it.
-
C.
returnedToCompetition
Indicates that an entity resumed participating in a competition after having previously stopped or been absent.
-
D.
hasReturnedToPlayIn
Indicates that an entity has resumed participating or performing in a particular event, context, or location after a period of absence.
-
E.
returnedToInternationalLeague
Indicates that an entity resumed participation or involvement in an international league after having previously left or been absent from it.
- 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_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8294e0fe08190b018e840146e27ca |
completed | April 9, 2026, 10:33 p.m. |
| PD | Predicate disambiguation | batch_69d8086ecd6c81908f424864857762d6 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.