Triple
T27564640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BF Block area |
E695863
|
entity |
| Predicate | hasRoadNamingScheme |
P36245
|
FINISHED |
| Object | block-based layout |
—
|
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: block-based layout | Statement: [BF Block area, hasRoadNamingScheme, block-based layout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadNamingScheme Context triple: [BF Block area, hasRoadNamingScheme, block-based layout]
-
A.
hasStreetNamingPattern
chosen
Indicates that there is a characteristic or systematic way in which streets are named in relation to a given entity.
-
B.
hasRoadNumberSystem
Indicates that a place or region uses a specific system for assigning numbers to its roads or highways.
-
C.
isNamedRoadIn
Indicates that a specific named road is located within or belongs to a particular geographic area or region.
-
D.
hasJunctionNumberingScheme
Indicates the specific system or method used to assign numbers to junctions within a network (such as roads or railways).
-
E.
hasStreetNumberingSystem
Indicates that a location or area uses an organized system for assigning numbers to buildings or addresses along its streets.
- 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_69ef53891af88190a193c5e2a1dac9b1 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 27, 2026, 1:40 p.m.