Triple
T13527617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Einstein’s photon box |
E323051
|
entity |
| Predicate | responseInvolved |
P20198
|
FINISHED |
| Object | Bohr’s use of general relativity |
—
|
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: Bohr’s use of general relativity | Statement: [Einstein’s photon box, responseInvolved, Bohr’s use of general relativity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: responseInvolved Context triple: [Einstein’s photon box, responseInvolved, Bohr’s use of general relativity]
-
A.
passInvolved
Indicates that an entity is involved in a passing action, either as the passer, receiver, or otherwise participating party.
-
B.
rightInvolved
Indicates that an entity is involved in or associated with a legal or formal right held, exercised, or affected in a given context.
-
C.
involvedAction
Indicates that an entity participates in, performs, or is otherwise engaged in a specified action or activity.
-
D.
involvedResolution
Indicates that an entity participated in or contributed to the process of resolving a particular issue, conflict, or problem.
-
E.
responseTool
chosen
Indicates a tool, method, or mechanism used to produce, deliver, or manage a response in a given context.
- 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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafb8e0cc8190b47f6aeb8ced470e |
completed | April 12, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69dbae1046c48190b4ee98c6c9cb9d85 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:44 p.m.