Triple
T21873442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ritual (Nous sommes du soleil) |
E540066
|
entity |
| Predicate | positionInSuite |
P86951
|
FINISHED |
| Object | fourth movement |
—
|
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: fourth movement | Statement: [Ritual (Nous sommes du soleil), positionInSuite, fourth movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInSuite Context triple: [Ritual (Nous sommes du soleil), positionInSuite, fourth movement]
-
A.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
B.
partOfSuite
chosen
Indicates that one item is a component or module belonging to a larger suite or collection.
-
C.
positionInAct
Indicates the specific location or role that something occupies within a particular act or segment of a larger sequence or performance.
-
D.
positionInSet
Indicates that an entity occupies a specific position or rank within an ordered set or collection.
-
E.
positionInSector
Indicates the specific location or placement of an entity within a defined sector or sub-area.
- 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_69e0c478f59081909d54302b57fc1ce3 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0f337ab5c8190937a457d348c732b |
completed | April 28, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:01 p.m.