Triple
T35110367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Varosha |
E1013267
|
entity |
| Predicate | typicalStreetFeature |
P45553
|
FINISHED |
| Object | cobblestone 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: cobblestone pavement | Statement: [Varosha, typicalStreetFeature, cobblestone pavement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalStreetFeature Context triple: [Varosha, typicalStreetFeature, cobblestone pavement]
-
A.
roadFeature
Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related infrastructure.
-
B.
isPartOfStreetscape
chosen
Indicates that something forms a component or element within the overall layout or visual composition of a streetscape.
-
C.
isThoroughfareFor
Indicates that something serves as a route or passageway used for travel or transportation between places.
-
D.
streetSet
Indicates that a particular street belongs to, or is included within, a specified set or collection of streets.
-
E.
cityStreetUsed
Indicates that a particular city street is utilized or traversed in the course of some activity, route, or event.
- 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_69f76dd659d08190bcdc00d37caafb62 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.