Triple
T21494604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steiner tree problem |
E530318
|
entity |
| Predicate | edgeWeights |
P144607
|
FINISHED |
| Object | can represent Euclidean distances |
—
|
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: can represent Euclidean distances | Statement: [Steiner tree problem, edgeWeights, can represent Euclidean distances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: edgeWeights Context triple: [Steiner tree problem, edgeWeights, can represent Euclidean distances]
-
A.
edgeType
Indicates the specific kind or category of connection that exists between two related entities.
-
B.
edgeMultiplicity
Indicates how many parallel or repeated connections (edges) exist between the same pair of entities in a relationship.
-
C.
typicalEdge
Indicates a standard or representative connection between two entities, as opposed to a special or exceptional type of edge.
-
D.
formsEdgeOf
Indicates that one entity constitutes a boundary or outer limit of another entity.
-
E.
standardEdge
Indicates a basic or default connection or link between two entities, without any special properties or conditions.
- 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_69e0c45bd15481909fba5910765cdda2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea567244819091863350fedae3ae |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e6386c5a4481909c37f7de7e9fc025 |
completed | April 20, 2026, 2:30 p.m. |
Created at: April 16, 2026, 6:23 p.m.