Triple
T1306385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FA Trophy |
E27887
|
entity |
| Predicate | includesReplays |
P12106
|
FINISHED |
| Object | historically yes, in earlier rounds |
—
|
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: historically yes, in earlier rounds | Statement: [FA Trophy, includesReplays, historically yes, in earlier rounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesReplays Context triple: [FA Trophy, includesReplays, historically yes, in earlier rounds]
-
A.
usesInstantReplay
Indicates that an entity employs instant replay technology or review during an event, action, or decision process.
-
B.
hasReprise
Indicates that an action, theme, or element is repeated or returns after its initial occurrence.
-
C.
inningsPlayed
Indicates the number of innings in which an entity (typically a player or team) has participated during a game or season.
-
D.
hasReplayRuleHistorically
chosen
Indicates that a replay rule applied to an entity at some point in the past, regardless of whether it is still in effect now.
-
E.
isRematchOfFinal
Indicates that a match is a subsequent encounter replaying the same opponents and stakes as a previous final match.
- 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_69a496d7d83481908f83085854e51328 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c15490a88190872c3d2698a8f9c9 |
completed | March 1, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69a4bee9e4a88190b22ab2ee831a23c9 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.