Triple
T37038883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puerto Rico Highway 199 |
E916723
|
entity |
| Predicate | hasRoadSignSystem |
P142975
|
FINISHED |
| Object | Puerto Rico territorial highway markers |
—
|
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: Puerto Rico territorial highway markers | Statement: [Puerto Rico Highway 199, hasRoadSignSystem, Puerto Rico territorial highway markers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadSignSystem Context triple: [Puerto Rico Highway 199, hasRoadSignSystem, Puerto Rico territorial highway markers]
-
A.
hasRoadSignConvention
chosen
Indicates that there is an established standard or system governing the design, meaning, or usage of road signs in a given context.
-
B.
hasRoadSign
Indicates that one entity possesses, displays, or is associated with a particular road sign.
-
C.
hasRoadNumberSystem
Indicates that a place or region uses a specific system for assigning numbers to its roads or highways.
-
D.
hasAssociatedRoadSystem
Indicates that one entity is linked to, or served by, a particular road or roadway network.
-
E.
hasRoadCode
Indicates that an entity is associated with a specific road identification code used for classification or reference.
- 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_69f76e93ec4c8190be81cf87354d9155 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fed6da0390819096b88ef4714b144e |
completed | May 9, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69fed53517d081909966f31707625f1a |
completed | May 9, 2026, 6:33 a.m. |
Created at: May 3, 2026, 4:14 p.m.