Triple
T29286766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karaj–Chalus scenic route |
E742534
|
entity |
| Predicate | endingPointArea |
P10883
|
FINISHED |
| Object | near Chalus on the Caspian Sea |
—
|
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: near Chalus on the Caspian Sea | Statement: [Karaj–Chalus scenic route, endingPointArea, near Chalus on the Caspian Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endingPointArea Context triple: [Karaj–Chalus scenic route, endingPointArea, near Chalus on the Caspian Sea]
-
A.
endingPointResort
Indicates that a resort serves as the final or destination point of a route, trip, or journey.
-
B.
significanceArea
Indicates that a specified area holds particular importance, relevance, or impact within a given context or system.
-
C.
typicalEndpointArea
Indicates that a location or region is the usual or characteristic area where an endpoint (such as a process, structure, or event outcome) occurs or is situated.
-
D.
targetArea
chosen
Indicates the specific area or region that is the intended focus or destination of an action or effect.
-
E.
endpointOnPeninsula
Indicates that one endpoint of an object, path, or feature lies on or within the bounds of a peninsula.
- 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_69f09121ed8c8190b4cb27be3619c262 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6653ccf648190b65fb1141928e47e |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 12:58 p.m.