Triple
T3638167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boyer–Lindquist coordinates |
E77120
|
entity |
| Predicate | metricComponent |
P49748
|
FINISHED |
| Object | g_tt = -(1 - 2Mr/Σ) |
—
|
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: g_tt = -(1 - 2Mr/Σ) | Statement: [Boyer–Lindquist coordinates, metricComponent, g_tt = -(1 - 2Mr/Σ)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metricComponent Context triple: [Boyer–Lindquist coordinates, metricComponent, g_tt = -(1 - 2Mr/Σ)]
-
A.
metricType
Indicates the specific category or kind of measurement that a given metric represents.
-
B.
metricForm
Indicates that one entity is expressed or represented in a particular metric form or measurement format relative to another.
-
C.
metricDependsOn
Indicates that the value or definition of one metric is determined by, derived from, or otherwise reliant on another metric.
-
D.
metricSignature
Indicates that one mathematical object (typically a metric or space) has a specific signature characterizing the signs and multiplicities of its metric components.
-
E.
meter
Indicates a measurement relationship where one entity quantifies the length, distance, or extent of another in meters.
- F. None of above. chosen
Provenance (4 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_69ad85dd0be48190b738990cb20c4731 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc32a5d448190b24f379b8b2d4f9b |
completed | March 8, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69adb842be7c8190b7dfdb7c906f294c |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb902e61c81908f10494f828e260f |
completed | March 8, 2026, 5:59 p.m. |
Created at: March 8, 2026, 3:24 p.m.