Triple
T13031889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Néel wall |
E326460
|
entity |
| Predicate | canBeMovedBy |
P95135
|
FINISHED |
| Object | magnetic fields |
—
|
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: magnetic fields | Statement: [Néel wall, canBeMovedBy, magnetic fields]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeMovedBy Context triple: [Néel wall, canBeMovedBy, magnetic fields]
-
A.
movable
chosen
Indicates that an entity is capable of being moved or repositioned from one location to another.
-
B.
canBeMobilisedFor
Indicates that an entity is capable of being called upon, activated, or deployed for a particular purpose, task, or operation.
-
C.
canBeBorneBy
Indicates that one entity is capable of being carried, supported, or transported by another entity.
-
D.
usesMovement
Indicates that an entity performs or involves some form of movement as part of its action or behavior.
-
E.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as 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_69d8076cc45c81908123123f43e69266 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97efe72348190b52fb4068f5fb829 |
completed | April 10, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69d97dc39a0881908119c62e31bf6182 |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:54 p.m.