Triple
T38463692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chengdu Hunters |
E912511
|
entity |
| Predicate | homeVenuePlanned |
P87779
|
FINISHED |
| Object | Chengdu home arena |
—
|
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: Chengdu home arena | Statement: [Chengdu Hunters, homeVenuePlanned, Chengdu home arena]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeVenuePlanned Context triple: [Chengdu Hunters, homeVenuePlanned, Chengdu home arena]
-
A.
homeMeetsVenue
chosen
Indicates that a home team plays its scheduled match at a specified venue.
-
B.
homeVenueIncludes
Indicates that a specified venue is part of, contained within, or used as a home location by another entity.
-
C.
homeVenueFocus
Indicates a primary or central emphasis on a particular venue as the main location associated with an entity’s activities or presence.
-
D.
home venue type
Indicates the kind or category of place that serves as the primary location where an entity regularly hosts its events or activities.
-
E.
homeVenueStatus
Indicates the status or condition of an entity’s designated home venue (e.g., whether it is active, available, or in use).
- 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_69f76e861d8c81908559031dc66e3c15 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcce7afcd08190906cc3801152656a |
completed | May 7, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69fcccf140ec8190862d53388a5f40d7 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.