Triple
T29973146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS13 |
E761372
|
entity |
| Predicate | roadSystemPattern |
P168310
|
FINISHED |
| Object | grid-like street 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: grid-like street layout | Statement: [SS13, roadSystemPattern, grid-like street layout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadSystemPattern Context triple: [SS13, roadSystemPattern, grid-like street layout]
-
A.
roadSystem
Indicates a relationship where multiple roads are organized and connected as part of a larger, integrated transportation network or infrastructure.
-
B.
roadSystemLevel
Indicates the classification or hierarchy level of a road within a broader transportation or road network system.
-
C.
roadType
Indicates the classification or category of a road based on its functional or physical characteristics.
-
D.
roadAxis
Indicates a central reference line that defines the primary longitudinal direction or alignment of a road.
-
E.
roadFeature
Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related infrastructure.
- 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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6786fe3948190be625545e28e4cb7 |
completed | May 2, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 6:32 p.m.