Triple
T29588793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vivre |
E754096
|
entity |
| Predicate | hasMusicalNumberOrder |
P184376
|
FINISHED |
| Object | late in the show |
—
|
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: late in the show | Statement: [Vivre, hasMusicalNumberOrder, late in the show]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMusicalNumberOrder Context triple: [Vivre, hasMusicalNumberOrder, late in the show]
-
A.
hasMusicalNumberIn
Indicates that a musical number (song or performance) appears within or is featured in a specific work, scene, or production.
-
B.
hasMusical
Indicates that one entity features, includes, or is associated with a musical work, performance, or musical component.
-
C.
hasMusicalForm
Indicates that one entity (typically a musical work or piece) is characterized by or structured according to a particular musical form.
-
D.
hasMusicalArrangementCharacteristic
Indicates that a musical arrangement possesses a specific characteristic, feature, or quality.
-
E.
hasMusicalDirection
Indicates that one entity is responsible for guiding, supervising, or determining the musical interpretation and performance of another entity.
- 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_69f0ef836ac88190bd809dc58b5ec907 |
completed | April 28, 2026, 5:33 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. |
| PDg | Predicate description generation | batch_69f7b0e3917481908a394680d76743c3 |
completed | May 3, 2026, 8:32 p.m. |
Created at: April 28, 2026, 6:12 p.m.