Triple
T32100428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caguas–Humacao corridor |
E819832
|
entity |
| Predicate | hasComponentRoad |
P85887
|
FINISHED |
| Object | Puerto Rico Highway 30 |
E237338
|
NE 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: Puerto Rico Highway 30 | Statement: [Caguas–Humacao corridor, hasComponentRoad, Puerto Rico Highway 30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComponentRoad Context triple: [Caguas–Humacao corridor, hasComponentRoad, Puerto Rico Highway 30]
-
A.
hasRoadComponent
chosen
Indicates that something includes, contains, or is composed of a specific road-related part or element.
-
B.
hasComponentRoute
Indicates that one route includes another route as a constituent or subordinate part of its overall structure.
-
C.
hasRoadCode
Indicates that an entity is associated with a specific road identification code used for classification or reference.
-
D.
hasAssociatedRoadSystem
Indicates that one entity is linked to, or served by, a particular road or roadway network.
-
E.
hasRoadPass
Indicates that an entity possesses a valid authorization or permit required to use a specific road or road network.
- F. None of above.
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_69f34901106881908ea893ad504a08be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a0361c6d76481909332b28ab01b0ef7 |
completed | May 12, 2026, 5:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a365c5059e48190b9829bf525c9e84d |
completed | June 20, 2026, 9:24 a.m. |
| PD | Predicate disambiguation | batch_6a0360b3818c819084bbecf705475f4f |
completed | May 12, 2026, 5:17 p.m. |
Created at: May 1, 2026, 12:26 a.m.