Triple
T3048466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bohr–Einstein debates |
E83508
|
entity |
| Predicate | BohrPosition |
P45329
|
FINISHED |
| Object | defense of Copenhagen interpretation |
—
|
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: defense of Copenhagen interpretation | Statement: [Bohr–Einstein debates, BohrPosition, defense of Copenhagen interpretation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BohrPosition Context triple: [Bohr–Einstein debates, BohrPosition, defense of Copenhagen interpretation]
-
A.
positionB
Indicates that one entity occupies or is located at a specific position relative to another entity.
-
B.
positionInPeriodicTable
Indicates the placement or location of a chemical element within the structure of the periodic table.
-
C.
positionA
Indicates the spatial or ordered position of an entity A within a defined reference frame or sequence.
-
D.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
E.
hasAtomicRadius
Indicates that an entity possesses a specific atomic radius value, representing the size of its atoms.
- 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_69ad8b24924c8190a9bb6f61d519e4ae |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9baed3848190a8351d9c8c4edc79 |
completed | March 8, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69ad962195388190856013a2519c2b0f |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad9b272a408190ba0ce09bdeea76c9 |
completed | March 8, 2026, 3:52 p.m. |
Created at: March 8, 2026, 3:01 p.m.