Triple
T30799209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lidra Caddesi |
E784318
|
entity |
| Predicate | locatedWithinWalls |
P57262
|
FINISHED |
| Object | Venetian walls of Nicosia |
—
|
NE NERFINISHED |
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: Venetian walls of Nicosia | Statement: [Lidra Caddesi, locatedWithinWalls, Venetian walls of Nicosia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedWithinWalls Context triple: [Lidra Caddesi, locatedWithinWalls, Venetian walls of Nicosia]
-
A.
enclosesWithinBlackWall
Indicates that one entity completely surrounds another entity with a boundary or barrier characterized as a black wall.
-
B.
positionInWall
Indicates that one entity occupies a specific location or placement within a wall.
-
C.
locatedInTheInteriorOf
Indicates that one entity is situated entirely within the inner part or inside area of another entity, rather than on its surface or boundary.
-
D.
existsWithin
chosen
Indicates that one entity is located inside the spatial, temporal, or conceptual boundaries of another entity.
-
E.
locatedInFortress
Indicates that an entity is situated within the boundaries or interior of a fortress.
- 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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a011c64ff18819099195701bbecbb20 |
completed | May 11, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_6a011b7f7a508190b2ebb518fb7a2fe9 |
completed | May 10, 2026, 11:57 p.m. |
Created at: April 29, 2026, 8:42 p.m.