Triple
T35313583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toulouse Olympique |
E1019842
|
entity |
| Predicate | rejoinedCompetition |
P53395
|
FINISHED |
| Object | RFL League 1 2016 |
—
|
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: RFL League 1 2016 | Statement: [Toulouse Olympique, rejoinedCompetition, RFL League 1 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rejoinedCompetition Context triple: [Toulouse Olympique, rejoinedCompetition, RFL League 1 2016]
-
A.
returnedToCompetition
Indicates that an entity resumed participating in a competition after having previously stopped or been absent.
-
B.
returnToPlayCompetitionFor
Indicates that an entity resumes participating in a competition or match on behalf of another entity (such as a team, club, or organization).
-
C.
competedFor
Indicates that an entity took part in a contest, rivalry, or competition in pursuit of another entity (such as a prize, position, or resource).
-
D.
rejoinedLeagueName
chosen
Indicates that an entity has returned to and become a member again of a previously left league identified by its name.
-
E.
servedCompetition
Indicates that one entity provided service, participation, or representation in a competitive event or context involving 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7908ec35881909a42f954fb9fa16e |
completed | May 3, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.