Triple
T20542235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dirac current |
E504368
|
entity |
| Predicate | hasTimeComponent |
P140477
|
FINISHED |
| Object | j^0 = ψ^† ψ |
—
|
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: j^0 = ψ^† ψ | Statement: [Dirac current, hasTimeComponent, j^0 = ψ^† ψ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimeComponent Context triple: [Dirac current, hasTimeComponent, j^0 = ψ^† ψ]
-
A.
hasTimeDimension
Indicates that something possesses or is associated with a temporal aspect, such as duration, point in time, or time-based variation.
-
B.
hasTimeOptions
Indicates that an entity is associated with one or more selectable time choices or configurations.
-
C.
hasTimeIndication
Indicates that something includes, specifies, or is associated with a particular time-related indication (such as a timestamp, time period, or temporal marker).
-
D.
isTemporalComponentOf
Indicates that one entity represents a temporal part, phase, or time-bounded segment within the overall duration or existence of another entity.
-
E.
hasTemporalAttribute
Indicates that an entity is associated with a specific temporal property or characteristic, such as time, duration, or period.
- F. None of above. chosen
Provenance (4 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_69e0b4b476648190bc6019622ae54d3c |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a292dd1c8190b5c3031f3b44eb52 |
completed | April 20, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69e59fe5592c8190bb6122b784496d02 |
completed | April 20, 2026, 3:39 a.m. |
| PDg | Predicate description generation | batch_69e5a6a824748190bbe6192d73f3c613 |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:38 a.m.