Triple
T11114308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Zealand international cricket tests |
E262843
|
entity |
| Predicate | awayMatchesPlayedIn |
P97343
|
FINISHED |
| Object | overseas venues |
—
|
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: overseas venues | Statement: [New Zealand international cricket tests, awayMatchesPlayedIn, overseas venues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awayMatchesPlayedIn Context triple: [New Zealand international cricket tests, awayMatchesPlayedIn, overseas venues]
-
A.
supportsAwayMatchesOf
Indicates that one entity provides backing, resources, or endorsement specifically for the away matches played by another entity.
-
B.
matchesPlayedIn
Indicates that a particular match was played in a specified location, event, or competition context.
-
C.
playedHomeMatchesIn
Indicates that an entity (typically a sports team) hosted its home matches at a specified venue or location.
-
D.
awayGamesPerTeam
Indicates the number of games a team plays as the visiting (away) side.
-
E.
leagueMatchesPlayed
Indicates the number of matches an entity has participated in within a specific league competition.
- 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79aa637888190935e852281408356 |
completed | April 9, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69d7441cf8188190b8095f622c923156 |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750ca52ec8190a559432a5de106fd |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:27 p.m.