Triple
T25796274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Clifden |
E649690
|
entity |
| Predicate | classicStatus |
P160687
|
FINISHED |
| Object | British Classic winner |
—
|
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: British Classic winner | Statement: [Lord Clifden, classicStatus, British Classic winner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classicStatus Context triple: [Lord Clifden, classicStatus, British Classic winner]
-
A.
traditionalStatus
Indicates that one entity holds a customary, long-established, or culturally recognized role, condition, or standing in relation to another entity.
-
B.
classStatus
Indicates the current academic or enrollment standing of an entity within a class or course context.
-
C.
canonicalStatus
Indicates the formal or official standing of an entity within an established authoritative or normative system.
-
D.
traditionalClubStatus
Indicates that an entity holds a recognized, historically established status as a traditional club within a given context or organization.
-
E.
categoryStatus
Indicates the current state or condition assigned to a category within a given system or context.
- 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_69e7ab34f8c8819099f6c4dabdabf129 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f60459a53c8190bbd90e80890eebcd |
completed | May 2, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f603b90c94819088d62cb9489e95ff |
completed | May 2, 2026, 2:01 p.m. |
Created at: April 22, 2026, 6:30 a.m.