Triple
T9247798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shenandoah |
E222241
|
entity |
| Predicate | hasNotableArrangement |
P40307
|
FINISHED |
| Object | arrangements for mixed choir |
—
|
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: arrangements for mixed choir | Statement: [Shenandoah, hasNotableArrangement, arrangements for mixed choir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableArrangement Context triple: [Shenandoah, hasNotableArrangement, arrangements for mixed choir]
-
A.
notableArrangementType
Indicates that one entity is characterized by or associated with a particular notable type of arrangement or configuration of another entity.
-
B.
hasArrangement
Indicates that one entity possesses, follows, or is organized according to a particular configuration, setup, or ordering defined by another entity.
-
C.
hasLiveArrangement
Indicates that there is an active, ongoing arrangement or agreement currently in effect between the related entities.
-
D.
hasNotableComposer
Indicates that an entity is associated with a composer who is recognized as particularly significant or distinguished.
-
E.
hasArrangementFor
chosen
Indicates that one entity has an established plan, setup, or provision in place to accommodate, support, or serve another entity or purpose.
- 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_69ca841d2b18819089f9faf5b2c2aec0 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd05f55a848190a59e7087cc07f6ef |
completed | April 1, 2026, 11:48 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4e79e48190b3200247f4624867 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:31 p.m.