Triple
T340077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | black hole no-hair theorem |
E6813
|
entity |
| Predicate | testedBy |
P202
|
FINISHED |
| Object | ringdown phase observations of binary black hole mergers |
—
|
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: ringdown phase observations of binary black hole mergers | Statement: [black hole no-hair theorem, testedBy, ringdown phase observations of binary black hole mergers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testedBy Context triple: [black hole no-hair theorem, testedBy, ringdown phase observations of binary black hole mergers]
-
A.
testsIn
Indicates that one entity conducts or performs tests within, on, or using another entity.
-
B.
tests
Indicates that one entity examines, evaluates, or checks another entity or condition to determine its properties, performance, or correctness.
-
C.
commonTest
Indicates that two or more entities share the same test, testing procedure, or evaluation in common.
-
D.
testType
Indicates the specific category or kind of test associated with an entity or event.
-
E.
demonstratedBy
chosen
Indicates that something is shown, proven, or made evident through the actions, behavior, or example of a particular 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_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. |
Created at: Feb. 28, 2026, 1:08 p.m.