Triple
T24204237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Attitude Adjustment |
E600058
|
entity |
| Predicate | canBePerformedFrom |
P28366
|
FINISHED |
| Object | standing position |
—
|
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: standing position | Statement: [Attitude Adjustment, canBePerformedFrom, standing position]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBePerformedFrom Context triple: [Attitude Adjustment, canBePerformedFrom, standing position]
-
A.
canBePerformed
chosen
Indicates that a particular action or activity is possible to carry out under given conditions or by a specified agent.
-
B.
canPerform
Indicates that one entity has the ability, permission, or capacity to carry out a specific action or function on or with another entity.
-
C.
canBeInvokedBy
Indicates that one entity (such as a function, method, or operation) is able to be called, triggered, or executed by another entity.
-
D.
canBeInvokedFrom
Indicates that one entity (such as a function, method, or component) is able to be called or triggered directly from another specified context or entity.
-
E.
canBePassedTo
Indicates that one entity is capable of being transferred, handed over, or given to 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27ca38c148190ae65cd692567d43d |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:37 p.m.