Triple
T10866201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Invincibles (Preston North End) |
E256535
|
entity |
| Predicate | matchesWonLeague |
P15130
|
FINISHED |
| Object | 18 (1888–89 league season) |
—
|
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: 18 (1888–89 league season) | Statement: [The Invincibles (Preston North End), matchesWonLeague, 18 (1888–89 league season)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matchesWonLeague Context triple: [The Invincibles (Preston North End), matchesWonLeague, 18 (1888–89 league season)]
-
A.
wonLeagueCup
Indicates that a team or competitor achieved victory in a specific league cup competition or tournament.
-
B.
gamesWonBy
chosen
Indicates the number of games that have been won by a particular entity in a given context.
-
C.
numberOfWins
Indicates the count of times an entity has achieved victory in a relevant context or competition.
-
D.
mostGamesWonBy
Indicates that one entity holds the record for having won the greatest number of games compared to others in a given context.
-
E.
leagueMatchesPlayed
Indicates the number of matches an entity has participated in within a specific league competition.
- 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7516cebe881909ed358a7641f6a12 |
completed | April 9, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69d70d308dfc81908792f98cfb871392 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:20 p.m.