Triple
T6416928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salle Le Peletier |
E127851
|
entity |
| Predicate | wasMainVenueFrom |
P13342
|
FINISHED |
| Object | 1821 |
—
|
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: 1821 | Statement: [Salle Le Peletier, wasMainVenueFrom, 1821]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasMainVenueFrom Context triple: [Salle Le Peletier, wasMainVenueFrom, 1821]
-
A.
hasHostedVenue
Indicates that a particular venue has served as the location for hosting a specific event or activity.
-
B.
hasMajorVenue
chosen
Indicates that an entity is associated with a primary or principal venue where its main activities or events take place.
-
C.
previousVenue
Indicates that one venue was used or occupied before another in a sequence of venues.
-
D.
hasPrincipalVenue
Indicates that an entity has a primary or main venue where its activities, events, or operations predominantly take place.
-
E.
originalPerformanceVenue
Indicates the venue where a performance was first originally presented or premiered.
- 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_69c0083815208190a9b299b8e0640218 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c068ea06b08190901e0c0a18fd5170 |
completed | March 22, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69c060f5d4e481909d1366190607b586 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:42 p.m.