Triple
T27464636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le MUC |
E693143
|
entity |
| Predicate | fullClubNameReferred |
P49144
|
FINISHED |
| Object | Le Mans Football Club |
—
|
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: Le Mans Football Club | Statement: [Le MUC, fullClubNameReferred, Le Mans Football Club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullClubNameReferred Context triple: [Le MUC, fullClubNameReferred, Le Mans Football Club]
-
A.
clubFullName
Indicates the complete official name of a club as opposed to an abbreviation or short form.
-
B.
supportsClubFullName
Indicates that one entity provides backing, endorsement, or assistance to a sports club identified by its full official name.
-
C.
associatedClubCommonName
Indicates that there is a relationship linking an entity to the commonly used or popular name of a club with which it is associated.
-
D.
refersToSuccessfulClub
Indicates that one entity makes reference to or is associated with a club that is considered successful.
-
E.
refersToClubIdentity
chosen
Indicates that one entity is referencing, invoking, or otherwise making use of the identity, name, or defining characteristics of a particular club.
- 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_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 12:51 p.m.