Triple
T21426832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coro |
E528577
|
entity |
| Predicate | instrumentalForces |
P19640
|
FINISHED |
| Object | orchestra |
—
|
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: orchestra | Statement: [Coro, instrumentalForces, orchestra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: instrumentalForces Context triple: [Coro, instrumentalForces, orchestra]
-
A.
primaryInstrumentalForces
Indicates that the subject represents the main or dominant forces used to produce, drive, or effect the object.
-
B.
componentForces
Indicates that a force is decomposed into its constituent directional components that together produce the original overall force.
-
C.
instrumentalIn
chosen
Indicates that one entity serves as a crucial means, tool, or contributing factor in bringing about an outcome or enabling another entity’s action or effect.
-
D.
typeOfForcesDirected
Indicates that certain forces are oriented or directed toward a particular target, direction, or reference.
-
E.
axisForces
Indicates a relationship where one entity exerts or applies force along, around, or with respect to a particular axis defined by another entity.
- 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_69e0c455f3688190810bc96365791b0f |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee813db52c8190ac933bc6ec4dbf77 |
completed | April 26, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e61639ee288190889ffd500d1260f6 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:49 p.m.