Triple
T16531331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lundenwic |
E401572
|
entity |
| Predicate | situatedOutside |
P22652
|
FINISHED |
| Object | Roman city walls of Londinium |
—
|
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: Roman city walls of Londinium | Statement: [Lundenwic, situatedOutside, Roman city walls of Londinium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: situatedOutside Context triple: [Lundenwic, situatedOutside, Roman city walls of Londinium]
-
A.
isLocatedOnOutskirtsOf
Indicates that one entity is situated on the outer edge or peripheral area of another entity, rather than in its central or inner part.
-
B.
hasOutdoorLocation
Indicates that an entity is associated with or possesses a specific outdoor place or setting.
-
C.
isOutdoor
Indicates that an entity or activity takes place outside, in an open-air or non-enclosed environment.
-
D.
situatedOnSideOf
Indicates that one entity is located along or beside the lateral part or edge of another entity.
-
E.
liesOutside
chosen
Indicates that one entity is located entirely beyond the spatial or conceptual boundary of another entity.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32ed8075c81908ff47396879abd0c |
completed | April 18, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e296995d388190b88ebe189dce890d |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.