Triple
T4461571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wigner surmise |
E98265
|
entity |
| Predicate | PoissonFeature |
P52484
|
FINISHED |
| Object | no level repulsion |
—
|
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: no level repulsion | Statement: [Wigner surmise, PoissonFeature, no level repulsion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PoissonFeature Context triple: [Wigner surmise, PoissonFeature, no level repulsion]
-
A.
featuresSample
Indicates that an entity includes or presents a particular sample as one of its components or examples.
-
B.
compositionalFeature
Indicates that one entity is a structural or constituent feature that forms part of the composition or makeup of another entity.
-
C.
nestFeature
chosen
Indicates that one entity is a structural or functional component contained within, or forming part of, another entity.
-
D.
featuresMethod
Indicates that an entity includes or provides a particular method as part of its functionality or behavior.
-
E.
featuresWriter
Indicates that one entity serves as the writer or author responsible for creating or composing the other 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_69b3454a7c608190944f5455c8031d73 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35674f718819089388c3924dd1414 |
completed | March 13, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69b34f65f6448190abfadb2ae5658798 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:34 p.m.