Triple
T21049009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Relational quantum mechanics |
E518523
|
entity |
| Predicate | hasNotion |
P95389
|
FINISHED |
| Object | relative events |
—
|
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: relative events | Statement: [Relational quantum mechanics, hasNotion, relative events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotion Context triple: [Relational quantum mechanics, hasNotion, relative events]
-
A.
usesNotion
Indicates that one entity makes use of the Notion application or platform for its activities or purposes.
-
B.
hasKeyNotion
chosen
Indicates that one entity embodies or contains a central or fundamental concept relevant to another entity.
-
C.
hasNotabilityNote
Indicates that there is an associated note or annotation explaining the significance, prominence, or special relevance of the subject.
-
D.
notionOf
Indicates that one entity represents, expresses, or embodies the concept or idea of another entity.
-
E.
hasNotabilityCategory
Indicates that an entity is associated with a particular category that characterizes its type or area of notability.
- 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_69e0b5053ac48190921529544959e906 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fd79830881909fdac2f0ea48d28c |
completed | April 21, 2026, 4:30 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf6728881908a2a43a5c8804a2a |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:34 p.m.