Triple
T13998461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tillana |
E336761
|
entity |
| Predicate | typicalPositionInRecital |
P86740
|
FINISHED |
| Object | concluding piece |
—
|
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: concluding piece | Statement: [Tillana, typicalPositionInRecital, concluding piece]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPositionInRecital Context triple: [Tillana, typicalPositionInRecital, concluding piece]
-
A.
typicalRecipientPosition
Indicates the usual or expected spatial or organizational position where a recipient is located relative to the action or source.
-
B.
typicalPositionInSentence
Indicates the usual or most common position that an element occupies within the linear order of components in a sentence.
-
C.
positionInPerformance
chosen
Indicates the specific ordering or placement of an entity within a performance or sequence of performed elements.
-
D.
positionInAct
Indicates the specific location or role that something occupies within a particular act or segment of a larger sequence or performance.
-
E.
choirPosition
Indicates the relative placement or role an entity holds within a choir’s arrangement or structure.
- 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_69d81c645c5c8190b1fd16a285a1b78a |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2eb68ba88190bfaf10777d607bf3 |
completed | April 14, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69dd465dfbc4819090d8c61fd572d35f |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:19 p.m.