Triple
T28087210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joralemon Street |
E709856
|
entity |
| Predicate | isResidentialStreet |
P164029
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Joralemon Street, isResidentialStreet, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isResidentialStreet Context triple: [Joralemon Street, isResidentialStreet, true]
-
A.
hasMainResidentialStreet
Indicates that an entity is associated with or served by a specific primary street used predominantly for residential purposes.
-
B.
isInResidentialArea
Indicates that something is located within a residential area, such as a neighborhood or zone primarily designated for housing.
-
C.
isResidential
Indicates that something is used or designated primarily for people to live in, rather than for commercial, industrial, or other non-living purposes.
-
D.
isResidentialBuildingIn
Indicates that a residential building is located within or belongs to a specified geographic area or administrative region.
-
E.
isPrimarySurfaceStreetIn
Indicates that a street serves as a main or primary surface-level roadway within a specified area or jurisdiction.
- 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_69ef9b7037f0819095bb90eaccbcaf32 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6416fbf4081909b0913c337927fc4 |
completed | May 2, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 27, 2026, 8:56 p.m.