Triple
T27770415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2016–17 Serie A with Juventus FC |
E701727
|
entity |
| Predicate | homeMatchesVenue |
P8186
|
FINISHED |
| Object | Juventus Stadium |
—
|
NE NERFINISHED |
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: Juventus Stadium | Statement: [2016–17 Serie A with Juventus FC, homeMatchesVenue, Juventus Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeMatchesVenue Context triple: [2016–17 Serie A with Juventus FC, homeMatchesVenue, Juventus Stadium]
-
A.
homeMatchesCountry
Indicates that an entity’s home location is situated within the specified country.
-
B.
playedHomeMatchesIn
chosen
Indicates that an entity (typically a sports team) hosted its home matches at a specified venue or location.
-
C.
homeTeamForVenue
Indicates that a team is designated as the primary (home) team associated with a particular venue.
-
D.
countryTeamHomeVenueOf
Indicates that a particular venue serves as the designated home venue for a specific national team.
-
E.
homeVenueTeam1City
Indicates that a specific city serves as the home venue location for the first team in a given context 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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f637962be88190b63239f6e4b782f4 |
completed | May 2, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 4:34 p.m.