Triple
T311400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schwarzschild radius |
E7615
|
entity |
| Predicate | formulatedInTheory |
P9767
|
FINISHED |
| Object | 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: general relativity | Statement: [Schwarzschild radius, formulatedInTheory, general relativity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formulatedInTheory Context triple: [Schwarzschild radius, formulatedInTheory, general relativity]
-
A.
theorized
Indicates that one entity has proposed or developed a theoretical explanation or hypothesis about another entity or phenomenon.
-
B.
hasFormulation
Indicates that one entity is expressed, prepared, or configured in a particular form or composition defined by another entity.
-
C.
mathematicallyFormulatedBy
Indicates that something (such as a concept, model, or theory) is expressed or defined using mathematical formulations created by a particular agent.
-
D.
formulatedIn
chosen
Indicates that something was created, developed, or expressed within a particular context, place, or framework.
-
E.
appliesTheory
Indicates that an entity uses or implements a particular theory in analyzing, explaining, or addressing something.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea49636c8190a69cbd951fc0a4db |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e940b9e8819092b821ff17ed026b |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:07 p.m.