Triple
T10340776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landau levels |
E243121
|
entity |
| Predicate | areUsedToDetermine |
P98
|
FINISHED |
| Object | effective mass of charge carriers |
—
|
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: effective mass of charge carriers | Statement: [Landau levels, areUsedToDetermine, effective mass of charge carriers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areUsedToDetermine Context triple: [Landau levels, areUsedToDetermine, effective mass of charge carriers]
-
A.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
B.
eligibleUses
Indicates the types of actions, purposes, or contexts in which something is permitted or qualified to be used.
-
C.
isBelievedToBeUsedFor
Indicates that something is thought or assumed to serve a particular purpose or function, without certainty.
-
D.
usedFor
chosen
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
E.
designationUsedFor
Indicates that a particular name, label, or title is employed to refer to or identify a specific entity or role.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e91fdb2081909866c6ecf417d75a |
completed | April 7, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69d4df9dc3208190bf1bd106f44f6202 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 11:55 a.m.