Triple
T344535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FA Cup |
E6909
|
entity |
| Predicate | usesExtraTimeInLaterRounds |
P12107
|
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, usesExtraTimeInLaterRounds, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesExtraTimeInLaterRounds Context triple: [FA Cup, usesExtraTimeInLaterRounds, true]
-
A.
usesPitchClock
Indicates that an entity employs or is governed by a pitch clock to regulate the timing of pitches.
-
B.
regulatesTimeFor
Indicates that one entity controls, influences, or sets the timing or schedule of another entity’s activities or processes.
-
C.
decidedInRegulationTime
Indicates that the outcome of a contest or match was determined within the standard allotted duration, without requiring any extra time or tiebreak procedures.
-
D.
usesInstantReplay
Indicates that an entity employs instant replay technology or review during an event, action, or decision process.
-
E.
commitmentTiming
Indicates the point in time or period relative to an event or agreement when a commitment is made, becomes effective, or is expected to be fulfilled.
- 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.