Triple
T2282077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irrigación |
E51301
|
entity |
| Predicate | hasStreetNamingPattern |
P36245
|
FINISHED |
| Object | streets named after rivers |
—
|
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: streets named after rivers | Statement: [Irrigación, hasStreetNamingPattern, streets named after rivers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStreetNamingPattern Context triple: [Irrigación, hasStreetNamingPattern, streets named after rivers]
-
A.
hasStreetGridPattern
Indicates that an area’s street layout follows a structured, grid-like pattern of intersecting roads.
-
B.
isNumberedStreet
Indicates that a street is designated primarily by a number (e.g., "1st Street," "42nd Avenue") rather than by a proper name.
-
C.
hasJunctionNumbering
Indicates that a road or route is assigned a specific numbering system for its junctions or intersections.
-
D.
hasStreet
Indicates that an entity is located on, associated with, or identified by a particular street.
-
E.
hasJunctionNumberingScheme
Indicates the specific system or method used to assign numbers to junctions within a network (such as roads or railways).
- F. None of above. chosen
Provenance (4 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_69a88b08e4308190bdac9aebcca1c91a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc21c405881908c4df7bee36136fe |
completed | March 7, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69abbdb9aa3c819088d0316c5269a1c2 |
completed | March 7, 2026, 5:55 a.m. |
| PDg | Predicate description generation | batch_69abbe4368a88190956bc9ee89c0fd1f |
completed | March 7, 2026, 5:57 a.m. |
Created at: March 4, 2026, 7:48 p.m.