Triple
T30267796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FA Cup 1963–64 |
E769700
|
entity |
| Predicate | finalScoreForRunnerUp |
P38172
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [FA Cup 1963–64, finalScoreForRunnerUp, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalScoreForRunnerUp Context triple: [FA Cup 1963–64, finalScoreForRunnerUp, 2]
-
A.
runnerUpScore
chosen
Indicates the score achieved by the participant or entity that finished in second place in a competition or ranking.
-
B.
finalSecondLegScore
Indicates the score achieved in the second leg of a two-leg competition or matchup once that leg is completed.
-
C.
secondRoundRunnerUp
Indicates that an entity finished in third place (runner-up to the runner-up) in the second round of a competition or selection process.
-
D.
runnersUpPoints
Indicates the number of points awarded to an entity for finishing as a runner-up in a competition or ranking.
-
E.
secondRunnerUp
Indicates that one entity finished in third place in a competition or ranking relative to the others.
- 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_69f224856d9881908c7f0dd64f059672 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: April 29, 2026, 7:43 p.m.