Triple
T3170940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theme from "Something Good" (revised) |
E66335
|
entity |
| Predicate | hasRevisedForm |
P35338
|
FINISHED |
| Object | concert performance arrangement |
—
|
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: concert performance arrangement | Statement: [Theme from "Something Good" (revised), hasRevisedForm, concert performance arrangement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRevisedForm Context triple: [Theme from "Something Good" (revised), hasRevisedForm, concert performance arrangement]
-
A.
hasReformedForm
Indicates that an entity has a later, modified, or updated form that results from a process of reform or restructuring.
-
B.
revisionOf
chosen
Indicates that one entity is a modified or updated version of another earlier entity.
-
C.
hasWrittenForm
Indicates that an entity is associated with a specific written or textual representation.
-
D.
wasReissued
Indicates that an item, such as a document or edition, has been issued again after its original release.
-
E.
isFormallyAcceptedVersionOf
Indicates that one entity is the officially recognized or approved version of another, often superseding or formalizing an earlier or informal form.
- 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_69ad8585d7988190af37365331093ccd |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada66c043081908eb23a4fe3420a78 |
completed | March 8, 2026, 4:40 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0076b4819094628f1ad10b8f68 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.