Triple
T10828655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Via Sâmbăta Valley |
E255558
|
entity |
| Predicate | usedAsApproachTo |
P93856
|
FINISHED |
| Object | Romania’s highest peak |
—
|
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: Romania’s highest peak | Statement: [Via Sâmbăta Valley, usedAsApproachTo, Romania’s highest peak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsApproachTo Context triple: [Via Sâmbăta Valley, usedAsApproachTo, Romania’s highest peak]
-
A.
approaches
Indicates that one entity moves closer in position or state to another entity or reference point.
-
B.
includesApproach
Indicates that one entity incorporates, utilizes, or is characterized by a particular method, strategy, or approach in relation to another entity or context.
-
C.
controlledApproachesTo
Indicates that one entity regulates or manages the methods or ways in which another entity can be approached.
-
D.
isMajorApproachTo
chosen
Indicates that one method, route, or strategy serves as a primary or principal way of reaching, addressing, or dealing with another entity.
-
E.
controlledApproachTo
Indicates a deliberate, regulated, or carefully managed way of proceeding toward or dealing with another entity.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d734d3eab88190b30a3025b6b2b0bc |
completed | April 9, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69d70d25280c8190b648d7d1958b413a |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:19 p.m.