Triple
T30456966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Final Fantasy |
E774888
|
entity |
| Predicate | liveSetup |
P28573
|
FINISHED |
| Object | solo violin and loop pedal |
—
|
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: solo violin and loop pedal | Statement: [Final Fantasy, liveSetup, solo violin and loop pedal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liveSetup Context triple: [Final Fantasy, liveSetup, solo violin and loop pedal]
-
A.
canonicalSetup
Indicates that an entity is arranged or configured in its standard, officially accepted, or authoritative form.
-
B.
typicalSetup
chosen
Indicates that an entity is arranged, configured, or organized in its standard or commonly used setup relative to another entity or context.
-
C.
supportsUserSetups
Indicates that an entity provides functionality or compatibility for configurations or setups defined by the user.
-
D.
launchEnvironment
Indicates the specific context, configuration, or setting in which a launch or deployment action takes place.
-
E.
controlledInstallation
Indicates that an entity has authoritative oversight or management responsibility over the setup, configuration, or deployment of another 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_69f22494fb60819095d893de0284f886 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f686ed94188190b8f308ad05c0c0a8 |
completed | May 2, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69f678d2196c8190b9d0d2fcd47cc539 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:10 p.m.