Triple
T36291478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Route 20 |
E893239
|
entity |
| Predicate | majorAccessTo |
P22318
|
FINISHED |
| Object | Da Lat area |
—
|
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: Da Lat area | Statement: [National Route 20, majorAccessTo, Da Lat area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorAccessTo Context triple: [National Route 20, majorAccessTo, Da Lat area]
-
A.
mainAccessFor
Indicates that one entity serves as the primary means or route of access for another entity.
-
B.
majorAccessTown
chosen
Indicates that a location serves as a primary or significant access point to a town, such as a main route, gateway, or connection hub.
-
C.
majorPass
Indicates that an entity successfully completes or passes a significant or primary stage, requirement, or examination in relation to another entity or process.
-
D.
controlsAccessTo
Indicates that one entity regulates, manages, or determines the ability of another entity to reach, use, or interact with a resource, location, or service.
-
E.
majorFor
Indicates that an academic program, field of study, or specialization is the primary major associated with a particular student or degree.
- 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_69f76e4a61f0819084a2b68dbbb4efc6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffb69812808190a751853b30183e65 |
completed | May 9, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69ffb63bdda88190a9dd8426dc0bad43 |
completed | May 9, 2026, 10:33 p.m. |
Created at: May 3, 2026, 4:09 p.m.