Triple
T29992745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | positronium |
E761922
|
entity |
| Predicate | lifetimeDependsOn |
P40963
|
FINISHED |
| Object | spin state |
—
|
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: spin state | Statement: [positronium, lifetimeDependsOn, spin state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifetimeDependsOn Context triple: [positronium, lifetimeDependsOn, spin state]
-
A.
lifetimeRequirement
Indicates that one entity imposes or must satisfy a specified duration or lifespan condition in relation to another entity or context.
-
B.
lifetimeControlledBy
Indicates that the existence or duration of one entity is dependent on and ends with the controlling entity’s lifetime.
-
C.
durationDependsOn
chosen
Indicates that the length of time of one event or state is determined or influenced by another event, condition, or factor.
-
D.
statusDependsOn
Indicates that the status or state of one entity is determined or influenced by the status or state of another entity.
-
E.
dependency
Indicates that one entity relies on, is conditioned by, or cannot function or exist properly without 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6791c8e088190a0766badc1d3b5cd |
completed | May 2, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:39 p.m.