Triple
T24602638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madrid city street network |
E608870
|
entity |
| Predicate | hasExpansionPattern |
P156715
|
FINISHED |
| Object | 19th-century grid-like ensanche |
—
|
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: 19th-century grid-like ensanche | Statement: [Madrid city street network, hasExpansionPattern, 19th-century grid-like ensanche]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExpansionPattern Context triple: [Madrid city street network, hasExpansionPattern, 19th-century grid-like ensanche]
-
A.
hasExpansionType
Indicates that an entity is associated with a particular mode or category of expansion (such as how it grows, extends, or scales).
-
B.
hasExpansionName
Indicates that an entity has a specific name used for its expanded or extended form.
-
C.
hasExpansionModel
Indicates that one entity is associated with a specific model or schema used to define how it can be expanded, detailed, or elaborated.
-
D.
hasExpansion
Indicates that one entity serves as a larger, extended, or elaborated form of another entity.
-
E.
hasExpansionInterface
Indicates that an entity provides or supports an interface through which it can be expanded or extended with additional components or functionality.
- 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.