Triple
T616511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kerr metric |
E14416
|
entity |
| Predicate | solves |
P14252
|
FINISHED |
| Object | Einstein field equations in vacuum |
—
|
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: Einstein field equations in vacuum | Statement: [Kerr metric, solves, Einstein field equations in vacuum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: solves Context triple: [Kerr metric, solves, Einstein field equations in vacuum]
-
A.
solutionType
Indicates the specific category or kind of solution associated with an entity or problem.
-
B.
commonlySolvedBy
Indicates that a problem, task, or issue is typically addressed or resolved through a particular method, tool, or agent.
-
C.
isSolutionOf
chosen
Indicates that one entity is a correct answer or satisfies the conditions of a given problem, equation, or task.
-
D.
resolves
Indicates that one entity successfully finds a solution, answer, or outcome for a problem, conflict, or uncertainty involving another entity.
-
E.
admitsSolution
Indicates that a problem, system, or situation allows for or possesses at least one valid solution.
- 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_69a4934b17c881909ace8270e8ddd202 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e22f3688190a512bec3f0347814 |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49cfd15288190b4abdbd0bce3edcd |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.