Triple
T3025916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galle International Stadium |
E82573
|
entity |
| Predicate | firstODITeams |
P44708
|
FINISHED |
| Object | Sri Lanka vs India |
—
|
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: Sri Lanka vs India | Statement: [Galle International Stadium, firstODITeams, Sri Lanka vs India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstODITeams Context triple: [Galle International Stadium, firstODITeams, Sri Lanka vs India]
-
A.
oversightTools
Indicates that certain tools or mechanisms are used to monitor, review, or supervise the actions or performance of an entity.
-
B.
firstRecipientTeam
Indicates the team that initially receives something (such as an item, message, or responsibility) before any others.
-
C.
integratedTeam
Indicates that multiple parties work together as a single, coordinated unit with shared goals, processes, and responsibilities.
-
D.
hasTechnicalCommittees
Indicates that an entity maintains or is associated with one or more technical committees.
-
E.
associatedSeniorTeam
Indicates a relationship where a senior-level team is linked or connected to a given entity as its corresponding or responsible team.
- 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_69ad8b1fb34081908c1b873e2b7273e1 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9abc78b48190a5283e7407a78fe7 |
completed | March 8, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69ad961c430c8190ac48f2e3c7e7c649 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f6af3881909f4547967384114c |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 3 p.m.