Triple
T25320053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Culler–Vogtmann Outer space |
E634851
|
entity |
| Predicate | metricCondition |
P114092
|
FINISHED |
| Object | edge lengths are positive real numbers |
—
|
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: edge lengths are positive real numbers | Statement: [Culler–Vogtmann Outer space, metricCondition, edge lengths are positive real numbers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metricCondition Context triple: [Culler–Vogtmann Outer space, metricCondition, edge lengths are positive real numbers]
-
A.
metricComponent
Indicates a relationship where one element functions as a component or constituent part of a larger metric.
-
B.
metricType
Indicates the specific category or kind of measurement that a given metric represents.
-
C.
featuresCondition
chosen
Indicates that an entity includes, exhibits, or is characterized by a particular condition.
-
D.
angleCondition
Indicates that a specified geometric relationship holds between angles, such as equality, inequality, or a particular angular constraint.
-
E.
metricDependsOn
Indicates that the value or definition of one metric is determined by, derived from, or otherwise reliant on another metric.
- 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_69e75a9847c08190bb02990d06d5ffb7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4968d6e848190bcb8668b6dc3f183 |
completed | May 1, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:28 p.m.