Triple
T12017209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Denis Compton |
E286056
|
entity |
| Predicate | firstClassRuns |
P102805
|
FINISHED |
| Object | 38142 |
—
|
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: 38142 | Statement: [Denis Compton, firstClassRuns, 38142]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstClassRuns Context triple: [Denis Compton, firstClassRuns, 38142]
-
A.
firstOrdinary
Indicates that the subject is the first entity to hold or occupy an ordinary (non-special, standard) position, role, or status in a given sequence or context.
-
B.
firstLeadLeadRun
Indicates that an entity serves as the primary leading participant or performer in the initial lead role of a production or event.
-
C.
firstRunningWinner
Indicates that the subject is the first entity to win among those participating in a running event or race.
-
D.
firstPerformedAs
Indicates the initial occasion or context in which an entity (such as a work, role, or piece) was performed by a particular performer or group.
-
E.
firstRunTimePeriod
Indicates the initial time span or interval during which something first occurs, operates, or is in effect.
- 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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902b6ebbc8190b13c44a61c6f81b9 |
completed | April 10, 2026, 2:01 p.m. |
| PDg | Predicate description generation | batch_69d91006e14081909838412df082f794 |
completed | April 10, 2026, 2:58 p.m. |
Created at: April 8, 2026, 9:47 p.m.