Triple
T16405827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bob Wyatt |
E398424
|
entity |
| Predicate | testMatches |
P123302
|
FINISHED |
| Object | 40 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: 40 Test matches for England | Statement: [Bob Wyatt, testMatches, 40 Test matches for England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testMatches Context triple: [Bob Wyatt, testMatches, 40 Test matches for England]
-
A.
testMatchStatus
Indicates the current state or outcome of a specific test match within its lifecycle (e.g., scheduled, in progress, completed, or cancelled).
-
B.
usesMatchesFrom
Indicates that one entity relies on or incorporates matches (e.g., pattern matches, rule matches, or result matches) produced by another entity or process.
-
C.
includesMatch
Indicates that one entity contains or encompasses a particular match or matching instance of another entity.
-
D.
matchResult
Indicates the outcome or final status produced by a particular match or game between participants.
-
E.
includesMatchType
Indicates that one entity’s set or collection contains an element with a specified type of match (e.g., exact, partial, or pattern-based) to another entity.
- 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e327d2b4e48190b7153f198639e9cd |
completed | April 18, 2026, 6:42 a.m. |
| PD | Predicate disambiguation | batch_69e226fe1dd08190865c181721f8c348 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:09 a.m.