Triple
T3203507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greyfriars, Newgate, London |
E67104
|
entity |
| Predicate | locatedWithinCityWall |
P16509
|
FINISHED |
| Object | London city wall near Newgate |
—
|
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: London city wall near Newgate | Statement: [Greyfriars, Newgate, London, locatedWithinCityWall, London city wall near Newgate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedWithinCityWall Context triple: [Greyfriars, Newgate, London, locatedWithinCityWall, London city wall near Newgate]
-
A.
locatedInFortress
Indicates that an entity is situated within the boundaries or interior of a fortress.
-
B.
surroundedCity
Indicates that one city is encircled or completely enclosed by another city or its surrounding territory.
-
C.
humanSettlementInside
chosen
Indicates that one human settlement is located entirely within the geographic boundaries of another area or settlement.
-
D.
containsFortress
Indicates that a location or area includes a fortress within its boundaries.
-
E.
isFortifiedCity
Indicates that a city is strengthened with defensive structures or fortifications, such as walls, ramparts, or similar protective works.
- 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_69ad8589bd988190afa7ed2bdffb7b33 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada9b188a88190b7b5e9b3be9410db |
completed | March 8, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69ad9e078f7c8190813d9fcb4f5071fb |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.