Triple
T13070690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | city walls of Groningen |
E329446
|
entity |
| Predicate | remainsAs |
P44035
|
FINISHED |
| Object | traces in street layout |
—
|
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: traces in street layout | Statement: [city walls of Groningen, remainsAs, traces in street layout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: remainsAs Context triple: [city walls of Groningen, remainsAs, traces in street layout]
-
A.
remainedIn
Indicates that an entity stayed within or continued to be located in a particular place or state for a period of time.
-
B.
remnants
chosen
Indicates that parts or traces of something remain after the main portion has been removed, used, or destroyed.
-
C.
remainsLitDuring
Indicates that one entity continues to emit light or stay illuminated throughout the duration of another specified event or condition.
-
D.
remainsLocation
Indicates that the physical remains of an entity are located or kept at a specified place.
-
E.
survivesAs
Indicates that one entity continues to exist or persist in place of, or after the end or transformation 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_69d80771749c81909a6d9197b9504872 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d980ee6130819095d835e7ff6a8c5b |
completed | April 10, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69d9803d46688190bac6b7d208f08d01 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9 p.m.