Triple
T30501485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sooß |
E776147
|
entity |
| Predicate | isSpaNeighbor |
P169793
|
FINISHED |
| Object | Baden spa town |
—
|
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: Baden spa town | Statement: [Sooß, isSpaNeighbor, Baden spa town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSpaNeighbor Context triple: [Sooß, isSpaNeighbor, Baden spa town]
-
A.
isAdjacentTo
Indicates that one entity is directly next to or bordering another without anything of the same type in between.
-
B.
innerNeighbor
Indicates that one entity is directly adjacent to another entity on the inside or interior side of a boundary or structure.
-
C.
neighboringTo
Indicates that one entity is located directly adjacent or very close to another entity, sharing a common boundary or immediate vicinity.
-
D.
hasNeighborRelationshipWith
Indicates that one entity is located adjacent to or directly next to another entity, sharing a neighbor relationship.
-
E.
hasNeighboringSite
Indicates that one site is located adjacent to or directly next to another site.
- F. None of above. chosen
Provenance (4 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_69f22498c5d481908aaea89e6fab8280 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f687805b048190824b5c0bc8d09bab |
completed | May 2, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f6827a7b9c8190ab13605aacc81df9 |
completed | May 2, 2026, 11:02 p.m. |
Created at: April 29, 2026, 8:14 p.m.