Triple
T210621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bekenstein–Hawking entropy |
E4708
|
entity |
| Predicate | isModifiedBy |
P1121
|
FINISHED |
| Object | quantum gravity corrections |
—
|
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: quantum gravity corrections | Statement: [Bekenstein–Hawking entropy, isModifiedBy, quantum gravity corrections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isModifiedBy Context triple: [Bekenstein–Hawking entropy, isModifiedBy, quantum gravity corrections]
-
A.
amendedBy
chosen
Indicates that one entity has been modified, revised, or updated as a result of changes made by another entity.
-
B.
isUpdated
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or a reference point.
-
C.
createdBy
Indicates that something was brought into existence, produced, or authored through the actions or efforts of a specific agent or entity.
-
D.
draftedBy
Indicates that something (such as a document, plan, or version) was created or written in its initial form by a particular agent or author.
-
E.
editedBy
Indicates that one entity has revised, modified, or otherwise made editorial changes to another 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_69a2575cb1dc8190a01ad332426dc339 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25d35aa288190966b6e15af1525cb |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b4f71b88190866c8262922ae204 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:52 a.m.