Triple
T23657086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FA Cup 1946–47 |
E584332
|
entity |
| Predicate | includedThirdRoundProper |
P123272
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [FA Cup 1946–47, includedThirdRoundProper, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedThirdRoundProper Context triple: [FA Cup 1946–47, includedThirdRoundProper, true]
-
A.
hasThirdRound
chosen
Indicates that an entity includes, participates in, or is associated with a third round within a multi-round process or sequence.
-
B.
includesSecondRound
Indicates that the referenced process, event, or activity contains or involves a second round or phase as part of its structure.
-
C.
firstRoundThirdPlace
Indicates that an entity finished in third place in the first round of a competition or selection process.
-
D.
thirdPlaceQualifiedFor
Indicates that an entity finishing in third place has earned qualification or advancement to a subsequent stage, event, or competition.
-
E.
hasThirdPlaceMatch
Indicates that a competition or tournament includes a specific match played to determine the third-place finisher between the losing semifinalists or equivalent contenders.
- 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_69e248ffc0888190ae23c4731eb8b7ac |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b35c257c81909f7004c0a35be4e3 |
completed | April 29, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:49 p.m.