Triple
T16492896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Composite fermion |
E400608
|
entity |
| Predicate | movesIn |
P2926
|
FINISHED |
| Object | Reduced effective magnetic field |
—
|
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: Reduced effective magnetic field | Statement: [Composite fermion, movesIn, Reduced effective magnetic field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movesIn Context triple: [Composite fermion, movesIn, Reduced effective magnetic field]
-
A.
movesFrom
Indicates that an entity changes location by departing or originating from a specified place.
-
B.
movementIn
chosen
Indicates a relationship where an entity moves within, into, or inside a specified area, space, or container.
-
C.
commonMove
Indicates that two or more entities share the same movement or relocation event, occurring together or in an identical manner.
-
D.
movementFor
Indicates that one entity moves on behalf of, in support of, or as a representative action for another entity.
-
E.
usesMove
Indicates that an entity performs or executes a specific move or action.
- 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e30cb648190a52cb32896c4ac5a |
completed | April 18, 2026, 7:09 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:13 a.m.