Triple
T1018842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feynman path integral |
E21993
|
entity |
| Predicate | weightFactor |
P6679
|
FINISHED |
| Object | exp(iS/ħ) |
—
|
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: exp(iS/ħ) | Statement: [Feynman path integral, weightFactor, exp(iS/ħ)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weightFactor Context triple: [Feynman path integral, weightFactor, exp(iS/ħ)]
-
A.
weight
Indicates a relationship where a numerical value quantifies how heavy an entity is, often used to measure or compare mass or load.
-
B.
considersFactor
Indicates that one entity takes another entity into account as a factor when forming a judgment, decision, or evaluation.
-
C.
weightingMethod
chosen
Indicates how relative importance or influence is assigned to elements within a set, such as criteria, features, or data points, in a calculation or decision process.
-
D.
isHeavilyWeightedToward
Indicates that something is strongly biased or disproportionately oriented in favor of one side, option, or aspect over others.
-
E.
sectorWeighting
Indicates the proportion or emphasis assigned to a particular sector within a broader portfolio, index, or classification.
- 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_69a493c68e24819080ed0ee8bcfd5ce0 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7c6005081909d9e56114c532d14 |
completed | March 1, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69a4b7238d4c8190b22d6c2ac0ac4911 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.