Triple
T29413855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colin Cowdrey |
E745969
|
entity |
| Predicate | amongFirstToReach |
P167152
|
FINISHED |
| Object | 100 Test matches in world cricket |
—
|
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 in world cricket | Statement: [Colin Cowdrey, amongFirstToReach, 100 Test matches in world cricket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: amongFirstToReach Context triple: [Colin Cowdrey, amongFirstToReach, 100 Test matches in world cricket]
-
A.
firstToAchieve
Indicates that one entity was the earliest or initial entity to accomplish or attain a specified goal, status, or outcome before any others.
-
B.
correctsUpTo
Indicates that one entity adjusts or fixes another entity’s errors or deviations within a specified limit or tolerance.
-
C.
reaches
Indicates that one entity extends or moves until it makes contact with, attains, or arrives at another entity or point.
-
D.
tieForFirstPlace
Indicates that two or more competitors share the highest rank or score, resulting in no single clear winner.
-
E.
maximumReach
Indicates the greatest extent, distance, or limit that something can reach or influence within a given 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_69f0a79f6d5c8190a350baed0157e06f |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66a3b1e108190bec0049dc39f8926 |
completed | May 2, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 28, 2026, 2:59 p.m.