Triple
T623097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reissner–Nordström metric |
E14555
|
entity |
| Predicate | dependsOnParameter |
P4452
|
FINISHED |
| Object | mass parameter M |
—
|
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: mass parameter M | Statement: [Reissner–Nordström metric, dependsOnParameter, mass parameter M]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dependsOnParameter Context triple: [Reissner–Nordström metric, dependsOnParameter, mass parameter M]
-
A.
hasDependency
Indicates that one entity relies on or requires another entity in order to function, exist, or be fulfilled.
-
B.
determinedBy
Indicates that one entity’s state, value, or outcome is decided, controlled, or fully specified by another entity.
-
C.
endsOn
Indicates that one entity terminates or concludes precisely at the boundary or endpoint of another entity.
-
D.
powerDependsOn
Indicates that the power or effectiveness of one entity is contingent upon, or influenced by, another entity.
-
E.
hasParameter
chosen
Indicates that an entity is associated with a specific parameter that defines or constrains some aspect of its behavior, configuration, or characteristics.
- 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_69a49e41753881909f0faed720cc31bc |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49d0069d0819087c83b608f6fc053 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.