Triple
T344544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FA Cup |
E6909
|
entity |
| Predicate | hasPreliminaryRounds |
P12109
|
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, hasPreliminaryRounds, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPreliminaryRounds Context triple: [FA Cup, hasPreliminaryRounds, true]
-
A.
hasAutomaticPlayoffBids
Indicates that certain participants are guaranteed entry into a playoff competition without needing to qualify through regular selection or performance criteria.
-
B.
hasParticipants
Indicates that an event, activity, or situation involves one or more entities as participants in it.
-
C.
hasCompetition
Indicates that one entity is in a state of rivalry or contest with another entity, typically competing for the same goal, resource, or advantage.
-
D.
hasPrimaryMeeting
Indicates that an entity is associated with its main or most important meeting, distinguishing it from other meetings it may have.
-
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. chosen
Provenance (4 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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eb01261c81909280128b5ce75eff |
completed | Feb. 28, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69a2e9530c98819085025efe4e04aa7e |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea0a4c448190a8a179daa9b90645 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.