Triple
T26803334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Houston–Lyon 1986 concerts |
E671155
|
entity |
| Predicate | eventSeriesOf |
P26159
|
FINISHED |
| Object | Jean-Michel Jarre outdoor concerts |
—
|
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: Jean-Michel Jarre outdoor concerts | Statement: [Houston–Lyon 1986 concerts, eventSeriesOf, Jean-Michel Jarre outdoor concerts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventSeriesOf Context triple: [Houston–Lyon 1986 concerts, eventSeriesOf, Jean-Michel Jarre outdoor concerts]
-
A.
individualEvents
Indicates that the subject is associated with one or more distinct, separately identifiable events rather than a single aggregated or continuous occurrence.
-
B.
hasEventSeries
chosen
Indicates that an entity is associated with, or participates in, a sequence of related events forming a series.
-
C.
featuresEventsFor
Indicates that something presents, highlights, or includes specific events as part of its content or offering.
-
D.
eventName
Indicates the specific label or title assigned to identify an event within a system or context.
-
E.
eventIn
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
- 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_69eeb31fbd888190a82dac5822e453bc |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 4:24 a.m.