Triple
T23298234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pilot-wave theory |
E590230
|
entity |
| Predicate | postulatesDefiniteParticleTrajectories |
P151758
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [pilot-wave theory, postulatesDefiniteParticleTrajectories, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postulatesDefiniteParticleTrajectories Context triple: [pilot-wave theory, postulatesDefiniteParticleTrajectories, true]
-
A.
resultingTrajectory
Indicates the path or course that emerges as the outcome of a prior motion, interaction, or transformation.
-
B.
postVenusTrajectory
Indicates a trajectory or path followed by an object after it has passed by or interacted with Venus.
-
C.
trajectoryType
Indicates the kind or pattern of motion an entity follows along its path over time.
-
D.
trajectoryAssist
Indicates assistance provided in planning, adjusting, or optimizing the path or course of motion of an entity.
-
E.
originalPlannedOrbit
Indicates the initially intended or designed orbital path or parameters for an object before any changes or deviations occurred.
- 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_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. |
| PDg | Predicate description generation | batch_69f01d88b4ec8190a2a17a88e0eda178 |
completed | April 28, 2026, 2:38 a.m. |
Created at: April 17, 2026, 5:03 p.m.