Triple
T27464653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le MUC |
E693143
|
entity |
| Predicate | clubReferredPredecessor |
P137706
|
FINISHED |
| Object | Union Sportive du Mans |
—
|
NE NERFINISHED |
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: Union Sportive du Mans | Statement: [Le MUC, clubReferredPredecessor, Union Sportive du Mans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clubReferredPredecessor Context triple: [Le MUC, clubReferredPredecessor, Union Sportive du Mans]
-
A.
clubPredecessorOf
chosen
Indicates that one club existed earlier and was replaced or succeeded by another club in an organizational or historical sequence.
-
B.
refersToClubFrom
Indicates that one entity is referencing or pointing to a specific club as its related or associated club.
-
C.
associatedClubPredecessorState
Indicates that a club is linked to a predecessor entity that existed in an earlier state or form of the organization.
-
D.
clubRebrandedAs
Indicates that a sports club has changed its official name or identity to become another specified club.
-
E.
referralBy
Indicates that one entity was referred, recommended, or directed to another entity by a specific source or agent.
- 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_69ef538105548190a771cc5a0cf8c211 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62dfbe6508190a6871084c5afe20f |
completed | May 2, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 12:51 p.m.