Triple
T12650886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FA Cup 2009–10 with Chelsea |
E302153
|
entity |
| Predicate | doubleType |
P106002
|
FINISHED |
| Object | domestic league and cup double |
—
|
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: domestic league and cup double | Statement: [FA Cup 2009–10 with Chelsea, doubleType, domestic league and cup double]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doubleType Context triple: [FA Cup 2009–10 with Chelsea, doubleType, domestic league and cup double]
-
A.
floatType
Indicates that an entity has a specific floating-point data type or is categorized as a floating-point numeric value.
-
B.
worksAsDoubleFor
Indicates that one entity performs as a substitute or stand-in for another entity, typically in professional or performance contexts.
-
C.
deltaType
Indicates a classification of the kind or category of change (difference) that has occurred between two related states or versions.
-
D.
doubleBarrelled
Indicates that an entity has a compound or two-part form (often a name or identifier) joined together as a single unit.
-
E.
twinType
Indicates that one entity is classified as a specific type or category of twin in relation to another entity.
- 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_69d7bdec9f9c8190b4bac675b7588211 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617b07ec8190b714f04ae6654060 |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b78ce8819091f15dd5013e6da5 |
completed | April 10, 2026, 8:42 p.m. |
| PDg | Predicate description generation | batch_69d96179c7648190a05a13991d62bebb |
completed | April 10, 2026, 8:45 p.m. |
Created at: April 9, 2026, 5:18 p.m.