Triple
T21771920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tahla |
E537453
|
entity |
| Predicate | roadConnectionRole |
P25845
|
FINISHED |
| Object | local hub between lowlands and Rif interior |
—
|
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: local hub between lowlands and Rif interior | Statement: [Tahla, roadConnectionRole, local hub between lowlands and Rif interior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadConnectionRole Context triple: [Tahla, roadConnectionRole, local hub between lowlands and Rif interior]
-
A.
roadJunctionRelation
Indicates a spatial connection where two or more roads meet, intersect, or join at a junction.
-
B.
linkedByRoadTo
Indicates that two locations are directly connected to each other by a road suitable for travel.
-
C.
roadJunctionIncludes
Indicates that a road junction spatially contains or encompasses a specific road segment or related roadway element as part of its structure.
-
D.
roadSystemRole
chosen
Indicates the specific functional role or responsibility an entity has within a road or transportation network system.
-
E.
roadConnectivityStatus
Indicates the current state of whether and how well two locations are connected by a road network.
- 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_69e0c470759c819094a215757113562b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f031af6a488190a2dcebed43d199d4 |
completed | April 28, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:51 p.m.