Triple
T35869018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madeira archipelago urban network |
E1037169
|
entity |
| Predicate | hasInfrastructureLinkType |
P20417
|
FINISHED |
| Object | road network |
—
|
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: road network | Statement: [Madeira archipelago urban network, hasInfrastructureLinkType, road network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInfrastructureLinkType Context triple: [Madeira archipelago urban network, hasInfrastructureLinkType, road network]
-
A.
hasInfrastructureType
Indicates that an entity possesses or is associated with a specific category or type of infrastructure.
-
B.
isTransportationLinkBetween
Indicates that there exists a transportation connection (such as a road, rail, air, or sea route) linking the two entities.
-
C.
linkType
chosen
Indicates the specific kind or category of relationship that connects two linked entities.
-
D.
isPartOfInfrastructureType
Indicates that something belongs to, or is categorized under, a specific type of infrastructure.
-
E.
hasBridgeTo
Indicates that one entity is connected to another by a bridge or bridging structure that allows passage or linkage between them.
- 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_69f76e1d279c8190843e5b64a0a12c3f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0082989e6c819099fea0e706332e37 |
completed | May 10, 2026, 1:05 p.m. |
| PD | Predicate disambiguation | batch_6a0081ed6a1481908baf472876e28db9 |
completed | May 10, 2026, 1:02 p.m. |
Created at: May 3, 2026, 4:06 p.m.