Triple
T32443046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nehru Cup |
E829064
|
entity |
| Predicate | typicalHostStadium |
P72058
|
FINISHED |
| Object | Jawaharlal Nehru Stadium, New Delhi |
E163805
|
NE 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: Jawaharlal Nehru Stadium, New Delhi | Statement: [Nehru Cup, typicalHostStadium, Jawaharlal Nehru Stadium, New Delhi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalHostStadium Context triple: [Nehru Cup, typicalHostStadium, Jawaharlal Nehru Stadium, New Delhi]
-
A.
hostStadium
Indicates that a particular stadium serves as the venue where an event, team, or competition is hosted.
-
B.
typicalVenueStadium
chosen
Indicates that the usual or characteristic venue for the referenced activity, event, or entity is a stadium.
-
C.
hostTeamStadium
Indicates that a particular team plays its home games at a specified stadium.
-
D.
hostStadiumType
Indicates the type or category of stadium that serves as the host venue for an event or activity.
-
E.
homeStadiumOf
Indicates that a particular stadium serves as the primary home venue for a specific sports team or organization.
- F. None of above.
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_69f3491d2e5c819092b1c9535beff8ec |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a344f37f23081908983f9c745f3ab55 |
completed | June 18, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:55 a.m.