Triple
T2092601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zeeman effect |
E32703
|
entity |
| Predicate | reveals |
P5035
|
FINISHED |
| Object | information about atomic energy levels |
—
|
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: information about atomic energy levels | Statement: [Zeeman effect, reveals, information about atomic energy levels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reveals Context triple: [Zeeman effect, reveals, information about atomic energy levels]
-
A.
discloses
chosen
Indicates that one entity reveals, makes known, or provides previously non-public information to another entity or to the public.
-
B.
exposes
Indicates making something visible, known, or vulnerable by removing cover, concealment, or protection.
-
C.
revealedSecretOf
Indicates that one entity has disclosed or exposed confidential or previously unknown information belonging to another entity.
-
D.
revealedAfter
Indicates that one piece of information, event, or state becomes known or disclosed only subsequent to another specified point in time or condition.
-
E.
revealedBefore
Indicates that one entity becomes known, disclosed, or made apparent earlier in time than 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_69a885eba0708190999696a45cbec816 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abba774ca881909f83cf65ffeb24bb |
completed | March 7, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69abb7b6274081909df36cd7a7c6a675 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.