Triple
T24351102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quadratestadt |
E613790
|
entity |
| Predicate | hasReferenceContext |
P102510
|
FINISHED |
| Object | urban design of Mannheim |
—
|
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: urban design of Mannheim | Statement: [Quadratestadt, hasReferenceContext, urban design of Mannheim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReferenceContext Context triple: [Quadratestadt, hasReferenceContext, urban design of Mannheim]
-
A.
hasReferences
chosen
Indicates that one entity cites, points to, or relies on another entity as a reference or source.
-
B.
hasRuleContext
Indicates that an entity is associated with, governed by, or interpreted within a specific rule or set of rules that define its contextual behavior or constraints.
-
C.
hasCanonicalContext
Indicates that something is associated with its primary, standard, or officially recognized contextual setting or framework.
-
D.
hasReferenceID
Indicates that an entity is associated with a specific reference identifier used to uniquely track or distinguish it.
-
E.
hasDocumentContext
Indicates that a document is associated with, or interpreted within, a specific contextual framework or situation.
- 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_69e2d7ddd29481909e7f539a6072bd71 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293457120819098af138fdd01846d |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:59 a.m.