Triple
T2379734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Willahelm |
E46281
|
entity |
| Predicate | meaningOfElement_will |
P16024
|
FINISHED |
| Object | will, desire, determination |
—
|
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: will, desire, determination | Statement: [Willahelm, meaningOfElement_will, will, desire, determination]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meaningOfElement_will Context triple: [Willahelm, meaningOfElement_will, will, desire, determination]
-
A.
followsWillOf
Indicates that one entity acts in accordance with, or submits its decisions and behavior to, the intentions, desires, or directives of another entity.
-
B.
wouldProvide
Indicates that one entity is willing or expected to supply or furnish something to another entity under certain conditions.
-
C.
viewOfWill
Indicates a relationship where something represents, expresses, or reflects the will, intention, or volition of an agent.
-
D.
will
Indicates that an entity is going to perform an action or be in a certain state in the future.
-
E.
meaningComponent
chosen
Indicates that one entity represents a semantic or conceptual component contributing to the overall meaning of 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_69a88a1554a48190a0180682bcf099be |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abc7b60c8c819080e4f682e4362a93 |
completed | March 7, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69abc59f73f08190924a36d7d475d8f4 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.