Triple
T29413849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colin Cowdrey |
E745969
|
entity |
| Predicate | matchesInTests |
P102804
|
FINISHED |
| Object | 114 |
—
|
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: 114 | Statement: [Colin Cowdrey, matchesInTests, 114]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matchesInTests Context triple: [Colin Cowdrey, matchesInTests, 114]
-
A.
testMatches
Indicates that a given test case or pattern corresponds to, satisfies, or correctly aligns with a specified input, condition, or expected outcome.
-
B.
testsIn
Indicates that one entity conducts or performs tests within, on, or using another entity.
-
C.
numberOfTestMatches
chosen
Indicates the total count of test matches associated with a given entity (such as a player, team, or series) in the relationship.
-
D.
containsTest
Indicates that one entity includes or encompasses another entity as a test or testing component.
-
E.
testMatchStatus
Indicates the current state or outcome of a specific test match within its lifecycle (e.g., scheduled, in progress, completed, or cancelled).
- 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_69f66a3b1e108190bec0049dc39f8926 |
completed | May 2, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 2:59 p.m.