Triple
T340085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | black hole no-hair theorem |
E6813
|
entity |
| Predicate | holdsFor |
P12018
|
FINISHED |
| Object | uncharged rotating black holes described by the Kerr metric |
—
|
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: uncharged rotating black holes described by the Kerr metric | Statement: [black hole no-hair theorem, holdsFor, uncharged rotating black holes described by the Kerr metric]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holdsFor Context triple: [black hole no-hair theorem, holdsFor, uncharged rotating black holes described by the Kerr metric]
-
A.
heldThat
Indicates that an entity (often a person or authority) maintained, asserted, or concluded that a particular proposition or judgment is true.
-
B.
heldOn
Indicates that an event or activity takes place at a specific time, date, or occasion.
-
C.
held
Indicates that one entity physically grasped, carried, or kept another entity in its possession or control.
-
D.
holding
Indicates that one entity is physically grasping, carrying, or keeping another entity in its possession or control.
-
E.
mayHold
Indicates that one entity is permitted or allowed to possess, contain, or maintain another entity.
- 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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eae4fcc08190bd4c2bf0149c8b50 |
completed | Feb. 28, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69a2e95067e88190a914a1c1d0283dfc |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea0a4c448190a8a179daa9b90645 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.