Triple
T34196057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emelecistas |
E877243
|
entity |
| Predicate | typicalMatchdayLocation |
P72058
|
FINISHED |
| Object | Estadio George Capwell stands |
E275237
|
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: Estadio George Capwell stands | Statement: [Emelecistas, typicalMatchdayLocation, Estadio George Capwell stands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMatchdayLocation Context triple: [Emelecistas, typicalMatchdayLocation, Estadio George Capwell stands]
-
A.
matchdayLocation
Indicates the venue or place where a particular matchday or game is held.
-
B.
typicalVenueStadium
chosen
Indicates that the usual or characteristic venue for the referenced activity, event, or entity is a stadium.
-
C.
isLocalStadiumFor
Indicates that a stadium serves as the primary home venue for a particular local team, club, or community.
-
D.
WorldCupVenue
Indicates that a location serves or has served as a venue where World Cup matches are held.
-
E.
locatedAtStadiumOfClub
Indicates that something is situated in the stadium that belongs to or is used by a particular sports club.
- 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_69f349af20a4819089ac24d28f2d8112 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36cc85da648190b504e88121faad64 |
completed | June 20, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:55 a.m.