Triple
T16403667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zwinger (outer ward) |
E398366
|
entity |
| Predicate | isLocatedRelativeTo |
P7317
|
FINISHED |
| Object | outside the main city wall of Nuremberg |
—
|
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: outside the main city wall of Nuremberg | Statement: [Zwinger (outer ward), isLocatedRelativeTo, outside the main city wall of Nuremberg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedRelativeTo Context triple: [Zwinger (outer ward), isLocatedRelativeTo, outside the main city wall of Nuremberg]
-
A.
isRelativeTo
Indicates that one entity has a familial or kinship relationship to another entity.
-
B.
hasRelativeLocation
chosen
Indicates that one entity is positioned in space in relation to another entity’s location.
-
C.
positionedRelativeTo
Indicates that one entity’s spatial location is defined or described in relation to the position of another entity.
-
D.
isRelatively
Indicates that one entity is being described, measured, or evaluated in relation to another entity or reference point, rather than in absolute terms.
-
E.
relativePosition
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
- 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e327d12dc08190a5b497692b667ed7 |
completed | April 18, 2026, 6:42 a.m. |
| PD | Predicate disambiguation | batch_69e226fe1dd08190865c181721f8c348 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:09 a.m.