Triple
T5445347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Town of Kraków |
E122234
|
entity |
| Predicate | formerlySurroundedBy |
P53799
|
FINISHED |
| Object | city walls |
—
|
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: city walls | Statement: [Old Town of Kraków, formerlySurroundedBy, city walls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerlySurroundedBy Context triple: [Old Town of Kraków, formerlySurroundedBy, city walls]
-
A.
previouslySurroundedBy
chosen
Indicates that an entity was, at some earlier time, completely encircled or enclosed by another entity or group of entities.
-
B.
surrounds
Indicates that one entity is located all around another entity, enclosing or encircling it on multiple sides or completely.
-
C.
formerlyLocatedOn
Indicates that an entity was once located on or situated upon another entity, but is no longer in that position.
-
D.
formerOccupant
Indicates that an entity previously occupied a position, role, or place but no longer does so.
-
E.
formerlyConnectedTo
Indicates that two entities were once connected or associated in some way, but that connection no longer exists.
- 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_69bd4640f52c81909e653ec361f66d76 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd95be329c81908783420cf81b6af5 |
completed | March 20, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69bd919e8d18819098c4af6a015e5cc2 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:07 p.m.