Triple
T17276388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lux aeterna |
E419401
|
entity |
| Predicate | hasPerformanceForces |
P120332
|
FINISHED |
| Object | unaccompanied choir |
—
|
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: unaccompanied choir | Statement: [Lux aeterna, hasPerformanceForces, unaccompanied choir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerformanceForces Context triple: [Lux aeterna, hasPerformanceForces, unaccompanied choir]
-
A.
typicalPerformanceForces
chosen
Indicates the forces that are normally or characteristically exerted or experienced during a given type of performance or operation.
-
B.
hasForceStrength
Indicates that one entity possesses a certain level or degree of physical or exerted force strength in relation to another entity or context.
-
C.
hasSecondaryForces
Indicates that an entity is subject to or associated with additional, indirect, or supporting forces beyond its primary forces.
-
D.
usesForces
Indicates that one entity applies physical, magical, or other types of forces to influence, move, or affect another entity.
-
E.
hasPerformanceElement
Indicates that one entity includes, contains, or is associated with a specific performance-related component or element.
- 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e4332625c48190a25bf51543d797c3 |
completed | April 19, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69e3832c3b98819091967ac7e91ba316 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:40 a.m.