Triple
T26205539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Five Live Yardbirds |
E655347
|
entity |
| Predicate | basedOnPerformance |
P148395
|
FINISHED |
| Object | club performance |
—
|
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: club performance | Statement: [Five Live Yardbirds, basedOnPerformance, club performance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnPerformance Context triple: [Five Live Yardbirds, basedOnPerformance, club performance]
-
A.
basedOnPerformanceBy
chosen
Indicates that something is derived from, adapted from, or determined according to the performance carried out by a particular entity.
-
B.
performanceBasis
Indicates that one entity’s performance is evaluated, determined, or justified on the basis of another specified factor, standard, or reference.
-
C.
basedOnBy
Indicates that one entity is derived from, justified by, or constructed using another entity as its source, foundation, or reference.
-
D.
basedOnValues
Indicates that something is determined, derived, or decided according to specified values or value-based criteria.
-
E.
basedOnPlayBy
Indicates that something (typically a creative work) is derived or adapted from a play authored by a specified entity.
- 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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 26, 2026, 8:50 p.m.