Triple
T32100461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caguas–Humacao corridor |
E819832
|
entity |
| Predicate | urbanAxisBetween |
P24772
|
FINISHED |
| Object | Caguas urban 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: Caguas urban area | Statement: [Caguas–Humacao corridor, urbanAxisBetween, Caguas urban area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanAxisBetween Context triple: [Caguas–Humacao corridor, urbanAxisBetween, Caguas urban area]
-
A.
cityAxis
Indicates a primary directional or structural line that organizes or defines the layout and orientation of a city.
-
B.
roadAxis
Indicates a central reference line that defines the primary longitudinal direction or alignment of a road.
-
C.
avenueRadiatingFrom
Indicates that one avenue extends outward from and is oriented away from another central point or thoroughfare, like a spoke radiating from a hub.
-
D.
streetOrientedAlong
Indicates that a street is aligned or runs in the same general direction as a specified reference feature or axis.
-
E.
routeBetween
chosen
Indicates that there exists a path or connection enabling travel or communication between two locations or points.
- 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_69f34901106881908ea893ad504a08be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 12:26 a.m.