Triple
T23825745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neon |
E589366
|
entity |
| Predicate | hasLiveArrangementVariation |
P153771
|
FINISHED |
| Object | solo acoustic |
—
|
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 acoustic | Statement: [Neon, hasLiveArrangementVariation, solo acoustic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiveArrangementVariation Context triple: [Neon, hasLiveArrangementVariation, solo acoustic]
-
A.
hasLiveArrangement
Indicates that there is an active, ongoing arrangement or agreement currently in effect between the related entities.
-
B.
hasArrangement
Indicates that one entity possesses, follows, or is organized according to a particular configuration, setup, or ordering defined by another entity.
-
C.
hasArrangementBy
Indicates that something (such as a work or piece) is in an arranged form created by a particular arranger.
-
D.
hasArrangementFor
Indicates that one entity has an established plan, setup, or provision in place to accommodate, support, or serve another entity or purpose.
-
E.
hasArrangementFeature
Indicates that one entity possesses a specific structural or spatial arrangement characteristic related to another entity or context.
- 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_69e25d1922d481909cab567c06a802ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7f114cc8190a8a557b7fd12c5c6 |
completed | April 29, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
| PDg | Predicate description generation | batch_69f158b0e320819090b947ee7eb14116 |
completed | April 29, 2026, 1:02 a.m. |
Created at: April 17, 2026, 8 p.m.