Triple
T28209210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calzada del Valle |
E711111
|
entity |
| Predicate | hasParallelAvenue |
P30057
|
FINISHED |
| Object | Calzada San Pedro |
—
|
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: Calzada San Pedro | Statement: [Calzada del Valle, hasParallelAvenue, Calzada San Pedro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParallelAvenue Context triple: [Calzada del Valle, hasParallelAvenue, Calzada San Pedro]
-
A.
hasParallelStreet
chosen
Indicates that one street runs parallel to another street, maintaining a constant distance without intersecting.
-
B.
hasParallelTransit
Indicates that one transit route, service, or segment runs in parallel to another along a similar path or corridor.
-
C.
hasParallelIn
Indicates that one entity has a corresponding or analogous counterpart in another context, system, or domain.
-
D.
hasNumberOfConvergingAvenues
Indicates the number of distinct avenues that meet or converge at a particular location or junction.
-
E.
hasCanalParallel
Indicates that one canal runs parallel to another canal without intersecting it.
- 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_69efb51cb5288190818c1f63a266af11 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: April 27, 2026, 10:37 p.m.