Triple
T16344115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kraków city walls |
E396884
|
entity |
| Predicate | defensiveElement |
P8412
|
FINISHED |
| Object | barbican |
—
|
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: barbican | Statement: [Kraków city walls, defensiveElement, barbican]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defensiveElement Context triple: [Kraków city walls, defensiveElement, barbican]
-
A.
defensiveStructure
chosen
Indicates a relationship where one entity functions as a structure built or used to protect, defend, or fortify another entity or area.
-
B.
defensiveSystem
Indicates a system or mechanism whose primary function is to protect, guard, or defend an entity against threats or attacks.
-
C.
defensiveRole
Indicates that an entity serves a protective or guarding function in relation to another entity or context.
-
D.
defensiveUse
Indicates that an entity uses something primarily for protection or defense against threats or attacks.
-
E.
defensiveSkillEmphasized
Indicates that particular focus or priority is placed on developing or utilizing defensive skills in the relevant context.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2da0c90e0819086f0a80a10cd79f3 |
completed | April 18, 2026, 1:10 a.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.