Triple
T36080673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Levitation Charm |
E1043636
|
entity |
| Predicate | requiresFocus |
P201084
|
FINISHED |
| Object | Concentration on target object |
—
|
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: Concentration on target object | Statement: [Levitation Charm, requiresFocus, Concentration on target object]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresFocus Context triple: [Levitation Charm, requiresFocus, Concentration on target object]
-
A.
mayProvideFocus
Indicates that one entity can potentially direct attention, emphasis, or concentration toward another entity or aspect.
-
B.
importFocus
Indicates that attention, priority, or emphasis is being brought into or concentrated on a particular entity or aspect.
-
C.
focusable
Indicates that an entity can receive input focus or become the active target for user interaction or navigation.
-
D.
canonicalFocus
Indicates that one entity is the primary or most representative focus or point of attention in relation to another entity.
-
E.
accessibilityFocus
Indicates that a particular user interface element is currently the primary target of accessibility tools, such as screen readers or keyboard navigation.
- 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_69f76e3154908190a6f702671c2bea08 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffc704e1e88190884928a6a5c55a87 |
completed | May 9, 2026, 11:45 p.m. |
| PD | Predicate disambiguation | batch_69ffc6b483d881908ad872e25fa6abc5 |
completed | May 9, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69ffc70423f08190bd7c0625b21147a4 |
completed | May 9, 2026, 11:45 p.m. |
Created at: May 3, 2026, 4:08 p.m.