Triple
T8900833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toward the Unknown Region |
E211924
|
entity |
| Predicate | usesForces |
P85138
|
FINISHED |
| Object | large chorus |
—
|
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: large chorus | Statement: [Toward the Unknown Region, usesForces, large chorus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesForces Context triple: [Toward the Unknown Region, usesForces, large chorus]
-
A.
associatedForce
Indicates that there is a force linked or connected to an entity, typically representing the physical influence acting on or exerted by that entity.
-
B.
includedForcesFrom
Indicates that one set of forces is derived from, or incorporated within, another set of forces.
-
C.
forces
Indicates that one entity compels or obliges another entity to perform an action or be in a certain state, typically against the latter’s will or without full freedom of choice.
-
D.
nativeForces
Indicates that certain forces or troops are indigenous to, or originate from, a particular place, group, or population.
-
E.
forcesAction
Indicates that one entity compels or coerces another entity to perform a specific action or behavior.
- 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_69ca83918d3081909b326fa3750cb8c8 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6428ffc48190814f6b865961dbd1 |
completed | April 1, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2bfb38819083d5eb1af8ccf4d6 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cffe8ec819084c12770fe0578f2 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:54 p.m.