Triple
T38331057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lenana |
E1037822
|
entity |
| Predicate | standardApproachRoute |
P183138
|
FINISHED |
| Object | Naro Moru route |
—
|
NE NERFINISHED |
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: Naro Moru route | Statement: [Lenana, standardApproachRoute, Naro Moru route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardApproachRoute Context triple: [Lenana, standardApproachRoute, Naro Moru route]
-
A.
standardApproach
Indicates that an entity uses or follows a commonly accepted, conventional, or typical method for addressing a task or problem.
-
B.
standardRouteStartsFrom
Indicates that a standard or predefined route has its starting point at a specified location or entity.
-
C.
standardRouteName
chosen
Indicates the officially designated or commonly accepted name used to identify a particular route.
-
D.
standardRouteSide
Indicates the usual or designated side of a route on which something (e.g., traffic, walking, or placement) is expected to occur or be positioned.
-
E.
onStandardRouteOf
Indicates that something lies along or follows the usual, predefined, or officially designated route of 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_69f76e20d65c81909619ac0dd85c56f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
Created at: May 3, 2026, 4:30 p.m.