Triple
T3572493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Born rule |
E75605
|
entity |
| Predicate | isEssentialFor |
P23639
|
FINISHED |
| Object | empirical predictions of quantum mechanics |
—
|
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: empirical predictions of quantum mechanics | Statement: [Born rule, isEssentialFor, empirical predictions of quantum mechanics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEssentialFor Context triple: [Born rule, isEssentialFor, empirical predictions of quantum mechanics]
-
A.
isImportantFor
Indicates that something holds significant value, relevance, or necessity in relation to something else.
-
B.
isNotRequiredFor
Indicates that one entity is not necessary or mandatory for the existence, occurrence, validity, or completion of another entity or process.
-
C.
isMandatoryFor
chosen
Indicates that something is required or compulsory for another thing to occur, be valid, or be completed.
-
D.
requiredBy
Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
-
E.
requires
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
- 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_69ad85d5e3008190bdfe0bacdd1f5a1b |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc0c447fc81909689259558187af4 |
completed | March 8, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69adb8364d848190a96a9bc7a6126af2 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:21 p.m.