Triple
T21555210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bunessan |
E531871
|
entity |
| Predicate | hasNotableArrangementFor |
P144223
|
FINISHED |
| Object | congregational singing |
—
|
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: congregational singing | Statement: [Bunessan, hasNotableArrangementFor, congregational singing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableArrangementFor Context triple: [Bunessan, hasNotableArrangementFor, congregational singing]
-
A.
notableArrangementOf
Indicates that one entity is a significant or noteworthy configuration, ordering, or spatial organization of the other entity.
-
B.
notableArrangementType
Indicates that one entity is characterized by or associated with a particular notable type of arrangement or configuration of another entity.
-
C.
hasArrangement
Indicates that one entity possesses, follows, or is organized according to a particular configuration, setup, or ordering defined by another entity.
-
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.
hasArrangementBy
Indicates that something (such as a work or piece) is in an arranged form created by a particular arranger.
- 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_69e0c460232c81908de2c3819d17c00e |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eed2df48c88190894b6b08a5cb6390 |
completed | April 27, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e633bf34c481909925d8dc1a633a65 |
completed | April 20, 2026, 2:10 p.m. |
Created at: April 16, 2026, 6:29 p.m.