Triple
T23298238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pilot-wave theory |
E590230
|
entity |
| Predicate | particleDynamicsGuidedBy |
P51619
|
FINISHED |
| Object | wave function |
—
|
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: wave function | Statement: [pilot-wave theory, particleDynamicsGuidedBy, wave function]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: particleDynamicsGuidedBy Context triple: [pilot-wave theory, particleDynamicsGuidedBy, wave function]
-
A.
dustDynamics
Indicates how dust particles move, interact, and evolve over time within a physical or astrophysical environment.
-
B.
involvesParticleEjection
Indicates that the action or process includes the emission or release of particles from a source.
-
C.
typicalDynamics
Indicates the usual or characteristic way in which a system, process, or interaction evolves or behaves over time.
-
D.
involvesParticleTransfer
Indicates that the relationship or action includes the movement or exchange of discrete particles from one entity to another.
-
E.
hasMicroscopicDynamics
chosen
Indicates that one entity exhibits or is characterized by underlying microscopic-level behaviors, processes, or interactions that govern its dynamics.
- 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_69e25d1c0ecc8190a355aa229f06d0e0 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f196d083188190abaae77dd4cf2bae |
completed | April 29, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69effcf325f88190b320268c3c551abb |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 5:03 p.m.