Triple
T37357024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allemanda |
E927481
|
entity |
| Predicate | typicalPositionInSuite |
—
|
GENERATED |
| Object | opening movement |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPositionInSuite Context triple: [Allemanda, typicalPositionInSuite, opening movement]
-
A.
typicalPositionType
Indicates the usual or most common positional role or placement type that an entity generally occupies or is associated with.
-
B.
typicalPositioning
Indicates the usual or characteristic spatial arrangement or placement of one entity relative to another or within a given context.
-
C.
typicalPositionInSentence
Indicates the usual or most common position that an element occupies within the linear order of components in a sentence.
-
D.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
E.
typicalCalendarPosition
Indicates the usual or standard placement of something within a calendar sequence, such as its customary date, time, or ordering.
- F. None of above. chosen
Provenance (1 batch)
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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:16 p.m.