Triple
T28196868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tie Your Mother Down |
E716470
|
entity |
| Predicate | hasLiveOpenerRoleIn |
P104295
|
FINISHED |
| Object | Queen 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: Queen concerts | Statement: [Tie Your Mother Down, hasLiveOpenerRoleIn, Queen concerts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiveOpenerRoleIn Context triple: [Tie Your Mother Down, hasLiveOpenerRoleIn, Queen concerts]
-
A.
hasLiveActionPerformer
Indicates that a character, role, or entity is portrayed or performed by a specific live-action (real-life) performer.
-
B.
hasOpening
Indicates that one entity possesses or features an opening, gap, or entrance that allows access, passage, or exposure.
-
C.
hasPlayingRole
Indicates that an entity participates in an activity, event, or performance in a specific playing role or capacity.
-
D.
hasPositionHolderRole
Indicates that an entity holds or occupies a specific position, office, or role within an organization or structure.
-
E.
isConcertOpener
chosen
Indicates that one performer, act, or event serves as the opening performance for another concert or main act.
- 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_69efd6b612f48190a72012b520afbd10 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: April 27, 2026, 10:28 p.m.