Triple
T24178462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porta Giuliana |
E599347
|
entity |
| Predicate | numberOfMainGatesOfNicosiaWalls |
P155601
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Porta Giuliana, numberOfMainGatesOfNicosiaWalls, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfMainGatesOfNicosiaWalls Context triple: [Porta Giuliana, numberOfMainGatesOfNicosiaWalls, 3]
-
A.
hasCityWallGates
Indicates that a city wall includes one or more gates that provide passage through it.
-
B.
hasCityWallsFrom
Indicates that a city’s defensive walls originate from, or were constructed starting at, a specified source location or structure.
-
C.
hasCityWallName
Indicates that a city wall is associated with a specific name or designation.
-
D.
hasCityWallFunction
Indicates that an entity serves the functional role of a city wall, such as providing defense, enclosure, or boundary protection for an urban area.
-
E.
numberOfCityGatesDestroyed
Indicates the quantity of city gates that have been destroyed in a given context or event.
- 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_69e288cca05481908faeb1563711114a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f27a753ca8819095706970d368f762 |
completed | April 29, 2026, 9:39 p.m. |
Created at: April 17, 2026, 11:34 p.m.