Triple
T30682531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Football League Championship 2013–14 |
E781091
|
entity |
| Predicate | containsClub |
P6630
|
FINISHED |
| Object | Leicester City F.C. |
—
|
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: Leicester City F.C. | Statement: [Football League Championship 2013–14, containsClub, Leicester City F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsClub Context triple: [Football League Championship 2013–14, containsClub, Leicester City F.C.]
-
A.
hasClub
Indicates that an entity is associated with or belongs to a particular club.
-
B.
hasClubBase
Indicates that a club or organization is based at, or primarily operates from, a particular location or facility.
-
C.
clubFrom
Indicates that one entity is the club or organization from which another entity originates, is affiliated, or is derived.
-
D.
involvesClub
chosen
Indicates that an action, event, or relationship includes or is associated with a specific club as a participating entity.
-
E.
appliesToClub
Indicates that something (such as a rule, policy, attribute, or action) is relevant or applicable specifically to 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ff255b84788190a94682f4efe1d0b8 |
completed | May 9, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69ff24f3ab108190bb017a656cff3d82 |
completed | May 9, 2026, 12:13 p.m. |
Created at: April 29, 2026, 8:33 p.m.