Triple
T24602639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madrid city street network |
E608870
|
entity |
| Predicate | hasPeripheralPattern |
P156716
|
FINISHED |
| Object | radial-concentric arterial system |
—
|
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: radial-concentric arterial system | Statement: [Madrid city street network, hasPeripheralPattern, radial-concentric arterial system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPeripheralPattern Context triple: [Madrid city street network, hasPeripheralPattern, radial-concentric arterial system]
-
A.
hasParityPatterns
Indicates that there is a specific pattern or regularity in the parity (odd/even characteristics) associated with the related entities.
-
B.
peripheralType
Indicates the specific category or kind of peripheral device associated with or used by an entity.
-
C.
hasBearingPattern
Indicates a relationship where an object or system exhibits or is characterized by a specific bearing arrangement or configuration pattern.
-
D.
hasStripePattern
Indicates that one entity exhibits a stripe-like visual pattern on its surface or body.
-
E.
hasHomeKitPattern
Indicates that there exists an associated configuration or pattern specifically intended for use with Apple HomeKit.
- 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_69e2c4d060e08190ac9f7c49b1036e20 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6ca751c8190a040c10d701ecf3a |
completed | April 30, 2026, 12:48 a.m. |
| PDg | Predicate description generation | batch_69f2b8b8bc5881908df49c0b07110246 |
completed | April 30, 2026, 2:04 a.m. |
Created at: April 18, 2026, 2:31 a.m.