Triple
T2126363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schwarzschild–Milne equations |
E46433
|
entity |
| Predicate | assumesGeometry |
P25627
|
FINISHED |
| Object | plane-parallel slab |
—
|
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: plane-parallel slab | Statement: [Schwarzschild–Milne equations, assumesGeometry, plane-parallel slab]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assumesGeometry Context triple: [Schwarzschild–Milne equations, assumesGeometry, plane-parallel slab]
-
A.
hasGeometry
chosen
Indicates that an entity is associated with a specific geometric representation or spatial form.
-
B.
assumes
Indicates that one entity takes on, accepts, or presumes a role, responsibility, state, or fact regarding another entity or situation.
-
C.
assumptionOnMap
Indicates that an assumption or inferred condition is applied to, or defined over, a specific map or mapping structure.
-
D.
relatesGeometryTo
Indicates a relationship in which one entity is associated with, defined by, or linked to a specific geometric representation or structure.
-
E.
isGeometric
Indicates that something has the properties or form of a geometric figure, pattern, or structure.
- 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_69a88a1626548190ae59a5028c3baa8e |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbb59182081908470f9be97e272c8 |
completed | March 7, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69abb7bd86cc8190938ef06c1ed6d969 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:44 p.m.