Triple
T23258582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Requiem |
E581940
|
entity |
| Predicate | hasTypicalForces |
P151570
|
FINISHED |
| Object | 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: choir | Statement: [Requiem, hasTypicalForces, choir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalForces Context triple: [Requiem, hasTypicalForces, choir]
-
A.
hasTypeOfForces
Indicates that one entity is associated with, or characterized by, a particular kind or category of forces.
-
B.
hasComponentForces
Indicates that a composite force is associated with, or can be decomposed into, specific component forces.
-
C.
hasSecondaryForces
Indicates that an entity is subject to or associated with additional, indirect, or supporting forces beyond its primary forces.
-
D.
hasForceStrength
Indicates that one entity possesses a certain level or degree of physical or exerted force strength in relation to another entity or context.
-
E.
typeOfForcesDirected
Indicates that certain forces are oriented or directed toward a particular target, direction, or reference.
- 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_69e246079f58819085eaa9c260906880 |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f194c710c48190aff03d210642a043 |
completed | April 29, 2026, 5:19 a.m. |
| PD | Predicate disambiguation | batch_69effce4d704819092826931d430e8c4 |
completed | April 28, 2026, 12:18 a.m. |
| PDg | Predicate description generation | batch_69f01d8770d081908897c28b04e5faea |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 17, 2026, 4:11 p.m.