Triple
T8278257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senegalese wrestling |
E193600
|
entity |
| Predicate | mainVenueType |
P41695
|
FINISHED |
| Object | open-air sand arenas |
—
|
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: open-air sand arenas | Statement: [Senegalese wrestling, mainVenueType, open-air sand arenas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainVenueType Context triple: [Senegalese wrestling, mainVenueType, open-air sand arenas]
-
A.
typicalVenues
Indicates that the specified locations are common or standard places where the associated activity, event, or entity usually occurs or is hosted.
-
B.
refersToVenueType
Indicates that one entity specifies or identifies the type or category of venue associated with another entity.
-
C.
venueComplex
Indicates that one venue is a complex or larger facility that contains or encompasses another venue.
-
D.
primaryVenueFor
Indicates that one entity serves as the main or principal venue or location for events, activities, or operations associated with another entity.
-
E.
home venue type
chosen
Indicates the kind or category of place that serves as the primary location where an entity regularly hosts its events or activities.
- 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_69ca82e217a48190880695635c44b2ed |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb79ebb6b88190bc777b8bd72fcdbc |
completed | March 31, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69cb70a4525481909399d313a6247ace |
completed | March 31, 2026, 6:58 a.m. |
Created at: March 30, 2026, 5:51 p.m.