Triple
T16338878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Test cricket |
E396743
|
entity |
| Predicate | homeAndAwaySeries |
P8330
|
FINISHED |
| Object | Test series |
—
|
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: Test series | Statement: [Test cricket, homeAndAwaySeries, Test series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeAndAwaySeries Context triple: [Test cricket, homeAndAwaySeries, Test series]
-
A.
homeAndAwayFormat
chosen
Indicates that a competition or matchup is structured so that each pair of opponents plays twice, once at each participant’s home venue and once away.
-
B.
homeSeries
Indicates that one entity serves as the primary or home series to which another entity (such as an episode, installment, or related work) belongs.
-
C.
hostsSeries
Indicates that an entity regularly presents, moderates, or leads a particular series (such as a show, event, or program).
-
D.
familyOrSeries
Indicates that two entities belong to the same family, collection, or series as related parts of a larger grouped set.
-
E.
houseOrFamily
Indicates that two entities are related through a shared house, household, or family membership.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2da08fbc88190a31127d10ca633d6 |
completed | April 18, 2026, 1:10 a.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.