Triple
T10622427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forest Hills Drive Tour |
E250233
|
entity |
| Predicate | hasOpeningActs |
P95018
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Forest Hills Drive Tour, hasOpeningActs, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpeningActs Context triple: [Forest Hills Drive Tour, hasOpeningActs, yes]
-
A.
wasOpeningActFor
Indicates that one performer or group served as the preliminary act appearing before another, main performer or group in a live event or show.
-
B.
openingPerformance
Indicates the performance or event that serves as the first or inaugural showing in a series, season, or run.
-
C.
hasOpeningCeremony
Indicates that an event or entity includes or is associated with a formal opening ceremony.
-
D.
hasLivePerformanceWith
Indicates that two or more entities participate together in the same live performance event.
-
E.
hasFanPerformances
Indicates that an entity has associated performances created or carried out by fans.
- F. None of above. chosen
Provenance (4 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6df7e5074819096668b53dcc9167a |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7fae088190973f70c69738af49 |
completed | April 8, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69d6df463ea8819091d6683e476b4f21 |
completed | April 8, 2026, 11:05 p.m. |
Created at: April 8, 2026, 8:51 p.m.