Triple
T18247104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jalsa Salana |
E436981
|
entity |
| Predicate | centralEventVenueType |
P115407
|
FINISHED |
| Object | purpose-built convention site |
—
|
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: purpose-built convention site | Statement: [Jalsa Salana, centralEventVenueType, purpose-built convention site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralEventVenueType Context triple: [Jalsa Salana, centralEventVenueType, purpose-built convention site]
-
A.
earlyVenue
Indicates that an event or activity takes place at a venue earlier than a standard, expected, or comparative time.
-
B.
hostVenueInstanceOf
chosen
Indicates that a specific host venue is an instance or concrete realization of a more general venue type or category.
-
C.
venue
Indicates the place or location where an event, activity, or interaction takes place.
-
D.
venueComplex
Indicates that one venue is a complex or larger facility that contains or encompasses another venue.
-
E.
rotatingVenue
Indicates that an event or activity takes place at different venues over time, rather than being fixed to a single location.
- 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_69d8b91104e08190a8241f7d260a5162 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4f7e7d49c8190b227a13b63615754 |
completed | April 19, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:33 a.m.