Triple
T29930630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love-In |
E760203
|
entity |
| Predicate | liveVenueType |
P164990
|
FINISHED |
| Object | rock ballroom |
—
|
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: rock ballroom | Statement: [Love-In, liveVenueType, rock ballroom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liveVenueType Context triple: [Love-In, liveVenueType, rock ballroom]
-
A.
internationalVenueFor
Indicates that a location serves as a host or site for events, activities, or functions involving participants or audiences from multiple countries.
-
B.
hasPerformanceVenueType
chosen
Indicates that an entity is associated with, or classified by, a particular type of performance venue.
-
C.
typicalVenues
Indicates that the specified locations are common or standard places where the associated activity, event, or entity usually occurs or is hosted.
-
D.
culturalVenue
Indicates a relationship where a place functions as a site for cultural activities, events, or institutions (such as museums, theaters, galleries, or cultural centers).
-
E.
locatedInVenueType
Indicates that an entity is situated within or associated with a venue of a specific type (e.g., stadium, theater, restaurant).
- 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_69f224631674819080c8d089674f9f4f |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f677cfd430819088e78639a293cc00 |
completed | May 2, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 6:17 p.m.