Triple
T29413854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colin Cowdrey |
E745969
|
entity |
| Predicate | firstToReach |
P21887
|
FINISHED |
| Object | 100 Test matches for England |
—
|
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: 100 Test matches for England | Statement: [Colin Cowdrey, firstToReach, 100 Test matches for England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstToReach Context triple: [Colin Cowdrey, firstToReach, 100 Test matches for England]
-
A.
amongFirstToReach
Indicates that an entity is one of the earliest individuals or groups to arrive at, achieve, or attain a particular place, state, or milestone.
-
B.
firstToAchieve
chosen
Indicates that one entity was the earliest or initial entity to accomplish or attain a specified goal, status, or outcome before any others.
-
C.
firstWinner
Indicates that the subject is the entity who achieved first place or victory in the referenced event or competition.
-
D.
tieForFirstPlace
Indicates that two or more competitors share the highest rank or score, resulting in no single clear winner.
-
E.
firstRunningWinner
Indicates that the subject is the first entity to win among those participating in a running event or race.
- 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_69f0a79f6d5c8190a350baed0157e06f |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a00d15f7b788190a3bf440be7837192 |
completed | May 10, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_6a00d0f8ef548190b1c15b06164eec4a |
completed | May 10, 2026, 6:39 p.m. |
Created at: April 28, 2026, 2:59 p.m.