Triple
T38489127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York zone |
E918004
|
entity |
| Predicate | hasPavingStyle |
P14456
|
FINISHED |
| Object | urban street pavement |
—
|
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: urban street pavement | Statement: [New York zone, hasPavingStyle, urban street pavement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPavingStyle Context triple: [New York zone, hasPavingStyle, urban street pavement]
-
A.
hasPavementPattern
Indicates that an entity possesses or is characterized by a specific pattern or design in its pavement surface.
-
B.
hasPavements
Indicates that a location or route is equipped with pavements (sidewalks) alongside it.
-
C.
pavedWith
chosen
Indicates that a surface or area is covered or constructed using a specified material as its paving.
-
D.
pavedBy
Indicates that a surface, route, or area has been covered or constructed with a hard material by a specified agent or process.
-
E.
hasPavementStatus
Indicates the type or condition of pavement associated with an entity, such as whether a surface is paved, unpaved, or its current pavement state.
- 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_69f76e9894208190a129a553a60ca58c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00868083b081909afc3d8d4ad56b43 |
completed | May 10, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_6a0084f5f72c8190b08afa82690e322a |
completed | May 10, 2026, 1:15 p.m. |
Created at: May 3, 2026, 4:31 p.m.