Triple
T938324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fulham F.C. |
E20246
|
entity |
| Predicate | historicLeague |
P5927
|
FINISHED |
| Object | First Division |
—
|
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: First Division | Statement: [Fulham F.C., historicLeague, First Division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicLeague Context triple: [Fulham F.C., historicLeague, First Division]
-
A.
formerLeague
chosen
Indicates that an entity previously belonged to or participated in a particular league but is no longer a member.
-
B.
originalLeague
Indicates the league or competition in which an entity (such as a team or club) initially participated or was first a member.
-
C.
playedInLeagueThatBecame
Indicates that an entity participated in a sports league which later transformed into, merged into, or was rebranded as another specified league.
-
D.
historicQuarterback
Indicates that the subject is recognized as a historically significant or notable quarterback in the context of the sport.
-
E.
hostsLeague
Indicates that one entity serves as the organizing or venue-providing host for a particular league.
- 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_69a493b0270c81909e6c9ce310f6aa55 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b388f0bc8190a087222636135ba5 |
completed | March 1, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69a4b29c68f48190aecad10e351a99de |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.