Triple
T34646261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St James’s Counterguard, Valletta |
E889701
|
entity |
| Predicate | cityFortificationOf |
P81783
|
FINISHED |
| Object | Valletta |
—
|
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: Valletta | Statement: [St James’s Counterguard, Valletta, cityFortificationOf, Valletta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityFortificationOf Context triple: [St James’s Counterguard, Valletta, cityFortificationOf, Valletta]
-
A.
isFortifiedCity
Indicates that a city is strengthened with defensive structures or fortifications, such as walls, ramparts, or similar protective works.
-
B.
fortifiedSite
chosen
Indicates a site that has been strengthened or defended with protective structures or measures against attack.
-
C.
fortressOriginallyBuiltBy
Indicates that a particular fortress was initially constructed by a specified builder or group.
-
D.
wasCitadelOf
Indicates that a place previously served as the main fortified stronghold or central defensive structure for another entity.
-
E.
fortifiedBuilding
Indicates that a building is strengthened or reinforced for defense against attacks or intrusions.
- 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_69f349d825c88190bfc6170ac9281260 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f72295f5948190a0a1b0e178999b2b |
completed | May 3, 2026, 10:25 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:04 a.m.