Triple
T25207029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Faulkner took 3 wickets for 36 runs |
E631280
|
entity |
| Predicate | matchStage |
P2703
|
FINISHED |
| Object | final |
—
|
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: final | Statement: [James Faulkner took 3 wickets for 36 runs, matchStage, final]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matchStage Context triple: [James Faulkner took 3 wickets for 36 runs, matchStage, final]
-
A.
matchOf
Indicates that one entity is a specific match, counterpart, or corresponding instance of another entity within a defined context or set.
-
B.
groupStageMatch
Indicates a match played between competitors during the group stage phase of a tournament or competition.
-
C.
competitionStage
chosen
Indicates the specific phase or round within a broader competition in which the related entities participate or are situated.
-
D.
qualificationStageIncluded
Indicates that a particular qualification stage is part of, or has been included within, a broader process, procedure, or evaluation sequence.
-
E.
matchLevel
Indicates the degree or extent to which two entities correspond, align, or are compatible with each other.
- 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_69e75a8b86c4819089eda22c843b739f |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f474bce13c8190bcdd22cdd70490b5 |
completed | May 1, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 12:52 p.m.