Triple
T13976744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deodhar Trophy matches |
E336205
|
entity |
| Predicate | statisticsRecorded |
P3976
|
FINISHED |
| Object | runs |
—
|
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: runs | Statement: [Deodhar Trophy matches, statisticsRecorded, runs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statisticsRecorded Context triple: [Deodhar Trophy matches, statisticsRecorded, runs]
-
A.
statusRecordedBy
Indicates that the status of an entity was documented or captured by a specific agent or system.
-
B.
statisticsConsidered
Indicates that certain statistics are taken into account or used as a basis in a decision, analysis, or evaluation involving the related entities.
-
C.
isFrequentlyRecorded
Indicates that an entity is captured or documented many times within a given dataset, medium, or context.
-
D.
hasStatistics
chosen
Indicates that an entity is associated with one or more statistical measures, records, or summaries describing its quantitative properties or performance.
-
E.
recorded
Indicates that one entity captured, stored, or documented information, audio, video, or data about another entity or event.
- 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_69d81c639e808190a0e4b4f3d31c6a59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e90dc148190b38e339aac0de484 |
completed | April 14, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69dd465a21408190b912a42c50ffa0d9 |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:18 p.m.