Triple
T38575693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rupin Street |
E929394
|
entity |
| Predicate | hasPublicSpaceCategory |
P192344
|
FINISHED |
| Object | street in Jerusalem |
—
|
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: street in Jerusalem | Statement: [Rupin Street, hasPublicSpaceCategory, street in Jerusalem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicSpaceCategory Context triple: [Rupin Street, hasPublicSpaceCategory, street in Jerusalem]
-
A.
hasPublicSpaces
Indicates that an entity includes or provides areas that are accessible and usable by the general public.
-
B.
hasPublicSpaceAlong
Indicates that a public space (such as a park, plaza, or walkway) is located adjacent to or runs alongside the referenced feature or element.
-
C.
hasPublicSpaceRole
Indicates that an entity holds a specific role, function, or responsibility within a public space.
-
D.
hasPublicSpaceElements
Indicates that something includes or incorporates features or components intended for use in public spaces.
-
E.
hasPublicSpacePolicy
Indicates that an entity has an established policy governing the use, management, or regulation of public spaces.
- 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_69f76ebd2248819083978362d81fa35e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
| PDg | Predicate description generation | batch_69fd05b965608190a3666410b9f8e125 |
completed | May 7, 2026, 9:35 p.m. |
Created at: May 3, 2026, 4:32 p.m.