Triple
T32834290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thou Art a Vineyard |
E839780
|
entity |
| Predicate | hasLaterArrangements |
P198063
|
FINISHED |
| Object | polyphonic choral settings |
—
|
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: polyphonic choral settings | Statement: [Thou Art a Vineyard, hasLaterArrangements, polyphonic choral settings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaterArrangements Context triple: [Thou Art a Vineyard, hasLaterArrangements, polyphonic choral settings]
-
A.
laterArrangementFor
Indicates that one arrangement, plan, or setup occurs after and supersedes another in time.
-
B.
laterArrangementBy
Indicates that one arrangement or configuration occurs after or succeeds another in time.
-
C.
hasArrangement
Indicates that one entity possesses, follows, or is organized according to a particular configuration, setup, or ordering defined by another entity.
-
D.
laterAttends
Indicates that one entity attends an event or place at a time later than another referenced attendance.
-
E.
hasArrangementFor
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. 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_69f3493f22f88190ae6dd4bc15b6cf8d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fec5c503808190bde0b1829ea43071 |
completed | May 9, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69fec535dd6c8190a6ab85201f5a04a9 |
completed | May 9, 2026, 5:25 a.m. |
| PDg | Predicate description generation | batch_69fec5c3f8248190b835a8e4eba470c4 |
completed | May 9, 2026, 5:27 a.m. |
Created at: May 1, 2026, 1:16 a.m.