Triple
T4704724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hull City A.F.C. |
E104364
|
entity |
| Predicate | reachedFinalInSeason |
P30655
|
FINISHED |
| Object | 2013–14 |
—
|
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: 2013–14 | Statement: [Hull City A.F.C., reachedFinalInSeason, 2013–14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reachedFinalInSeason Context triple: [Hull City A.F.C., reachedFinalInSeason, 2013–14]
-
A.
hasFinalMatch
chosen
Indicates that an entity is associated with a concluding or decisive match in a series, tournament, or competition.
-
B.
finalEditionSeason
Indicates that a given season is the final season (last edition) of a series or competition.
-
C.
grandFinalSeason
Indicates that an event, competition, or series represents the culminating or final season in a larger sequence or championship.
-
D.
occurredInSeason
Indicates that an event or occurrence took place during a specific season within a temporal sequence (such as a TV show season or sports season).
-
E.
reachedNBAFinalsInSeason
Indicates that a team or player advanced to and participated in the NBA Finals during a specified season.
- 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_69bd43e9b88481908582103dcadff3d9 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650ad0f88190844bfcb46b3071c2 |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd621ba7448190a53ab1e2897acf71 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:17 p.m.