Triple
T10355831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laban effort theory |
E243995
|
entity |
| Predicate | effortAction |
P58482
|
FINISHED |
| Object | Float |
—
|
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: Float | Statement: [Laban effort theory, effortAction, Float]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effortAction Context triple: [Laban effort theory, effortAction, Float]
-
A.
forcesAction
Indicates that one entity compels or coerces another entity to perform a specific action or behavior.
-
B.
attemptedAction
chosen
Indicates that an entity made an effort to perform a particular action, regardless of whether the action was successfully completed.
-
C.
hasPlanningEffort
Indicates that an entity is associated with a required or invested amount of planning work or preparation effort.
-
D.
hasReformEffort
Indicates that an entity undertakes, is involved in, or is the subject of a deliberate effort to change, improve, or restructure a system, policy, or practice.
-
E.
causeOfAction
Indicates that one entity is the reason or basis for initiating a legal action or lawsuit against 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_69d381b22b8c8190aaed476be5f872a9 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e953d4888190b7ca0ac932349dbf |
completed | April 7, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69d4dfa657f481909cc5cc8fec00ad19 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 11:58 a.m.