Triple
T35432385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La casa de la Fiera |
E1024097
|
entity |
| Predicate | associatedWithCityClub |
P102426
|
FINISHED |
| Object | León F.C. |
E203598
|
NE 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: León F.C. | Statement: [La casa de la Fiera, associatedWithCityClub, León F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCityClub Context triple: [La casa de la Fiera, associatedWithCityClub, León F.C.]
-
A.
usedByClubFromCity
Indicates that something (such as a facility, stadium, or resource) is utilized by a sports club that is based in a particular city.
-
B.
associatedWithCitySports
Indicates a relationship where an entity has a connection or involvement with city-level sports activities, organizations, or events.
-
C.
participatingClubsFromCity
Indicates that the clubs involved in an event or activity originate from or are based in a specified city.
-
D.
associatedWithClubSuccess
Indicates that an entity has a meaningful connection or contribution to the success or achievements of a club.
-
E.
relatedToClub
chosen
Indicates that there is an association or connection between an entity and a club, without specifying the exact nature of that relationship.
- F. None of above.
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_69f76df743c48190aecb6dd79efb0d95 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38726acd808190902b60b419f19dae |
completed | June 21, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.