Triple
T38058557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FA Cup 2005–06 |
E950270
|
entity |
| Predicate | properRoundsIncluded |
P153404
|
FINISHED |
| Object | first round proper |
—
|
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: first round proper | Statement: [FA Cup 2005–06, properRoundsIncluded, first round proper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: properRoundsIncluded Context triple: [FA Cup 2005–06, properRoundsIncluded, first round proper]
-
A.
hasProperRounds
Indicates that an entity is associated with rounds that meet specified standards or criteria for being considered proper or valid.
-
B.
includedRound
chosen
Indicates that a particular round is part of, or contained within, a larger set, sequence, or event of rounds.
-
C.
reachedRound
Indicates that an entity has advanced to or attained a particular round or stage within a process, event, or competition.
-
D.
scheduledRounds
Indicates that specific rounds or sessions have been planned and assigned to occur at designated times.
-
E.
hasRound
Indicates that an entity possesses, includes, or is associated with a particular round (e.g., a round of an event, game, or process).
- 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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc44c7e73c819082d4fc1900fb9632 |
completed | May 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69fbc8efffbc8190a139798ad1880526 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:21 p.m.