Triple
T32391048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cittadella |
E827673
|
entity |
| Predicate | hasWalkableRamparts |
P181778
|
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: [Cittadella, hasWalkableRamparts, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWalkableRamparts Context triple: [Cittadella, hasWalkableRamparts, yes]
-
A.
containsRamps
Indicates that one entity includes or is equipped with one or more ramps as part of its structure or features.
-
B.
hasRampSpace
Indicates that a location or structure includes designated space for a ramp, allowing sloped access between different levels.
-
C.
isWalkable
Indicates that an entity can be traversed on foot, typically without obstruction or restriction.
-
D.
hasWalkwayShape
Indicates that a walkway possesses a particular geometric or structural shape or configuration.
-
E.
towerAccessibleBy
Indicates that a tower can be reached or entered via a specified route, path, or means of access.
- 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7824dc3f0819092a5102895b4a478 |
completed | May 3, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f7817c79e081908e685c48165e086b |
completed | May 3, 2026, 5:10 p.m. |
Created at: May 1, 2026, 12:52 a.m.