Triple
T119037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medieval City of Rhodes |
E2403
|
entity |
| Predicate | hasCityWall |
P1495
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Medieval City of Rhodes, hasCityWall, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCityWall Context triple: [Medieval City of Rhodes, hasCityWall, yes]
-
A.
hasBellTower
Indicates that one entity (typically a building or structure) possesses or includes a bell tower as part of it.
-
B.
hasCityHall
Indicates that a location or administrative area possesses or is served by a specific city hall building or institution.
-
C.
castleBuiltFor
Indicates that a castle was constructed specifically for the benefit, use, or commission of a particular person, group, or purpose.
-
D.
hasUrbanFeature
chosen
Indicates that a place or area possesses a specific urban element or infrastructure feature (such as roads, parks, or buildings) as part of its built environment.
-
E.
hasHistoricCity
Indicates that an entity possesses, contains, or is associated with a city recognized for its historical significance.
- 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_69a2506c5428819085c28a8884790e29 |
completed | Feb. 28, 2026, 2:18 a.m. |
| NER | Named-entity recognition | batch_69a258e0b11c8190b7b5cf3c354c47ce |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a25646d5088190a057989c32da3a90 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:24 a.m.