Triple
T6378826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parisienne Walkways |
E143530
|
entity |
| Predicate | isOftenPerformedWithExtendedSolo |
P70279
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Parisienne Walkways, isOftenPerformedWithExtendedSolo, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOftenPerformedWithExtendedSolo Context triple: [Parisienne Walkways, isOftenPerformedWithExtendedSolo, true]
-
A.
hasImprovisedSoloBy
Indicates that an improvised solo performance is attributed to or performed by a specific entity.
-
B.
hasGuitarSolo
Indicates that an entity (such as a song or performance) contains or features a guitar solo.
-
C.
instrumentalSoloist
Indicates that an entity performs a featured solo part on a musical instrument within a work or performance.
-
D.
hasNotableSoloFor
Indicates that an individual is recognized for performing a prominent or distinguished solo part within a larger work or performance associated with another entity.
-
E.
isFrequentlyImprovisedOver
Indicates that one thing commonly serves as the underlying basis or structure over which improvisation is often performed.
- 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_69c008d9f4348190ab598a2913259a1c |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0683ed0788190b00f626c76a71ea2 |
completed | March 22, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69c060eff524819094cee1c70a0c1ff4 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623d23448190a75cf5d802fc0a02 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:33 p.m.