Triple
T20890091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICC Test Team of the Year selection |
E514384
|
entity |
| Predicate | isTeamFielded |
P115677
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [ICC Test Team of the Year selection, isTeamFielded, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTeamFielded Context triple: [ICC Test Team of the Year selection, isTeamFielded, false]
-
A.
fieldedCombinedTeamIn
Indicates that an entity organized and presented a joint or composite team to participate in a specified event or context.
-
B.
fieldedIn
chosen
Indicates that an entity was deployed, presented, or put into active use within a particular context, event, or domain.
-
C.
hasTeamInGame
Indicates that a particular game involves or includes a specific team as a participant.
-
D.
usesNumberOfPlayersOnFieldPerTeam
Indicates that the relationship specifies or depends on how many players each team has on the field at a given time.
-
E.
isHomeFieldOf
Indicates that a particular location or venue serves as the primary home field or home ground for a specific team or organization.
- 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_69e0b4f7ebe48190952a85547a0f31a1 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6d05d591481908c9c999db76760fc |
completed | April 21, 2026, 1:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:46 p.m.