Triple
T9558142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Singine District |
E230594
|
entity |
| Predicate | hasNeighboringEntity |
P5707
|
FINISHED |
| Object | other districts of the canton of Fribourg |
—
|
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: other districts of the canton of Fribourg | Statement: [Singine District, hasNeighboringEntity, other districts of the canton of Fribourg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNeighboringEntity Context triple: [Singine District, hasNeighboringEntity, other districts of the canton of Fribourg]
-
A.
hasNotableNearbyEntity
Indicates that one entity has another significant or noteworthy entity located in its close physical or contextual proximity.
-
B.
isAdjacentTo
chosen
Indicates that one entity is directly next to or bordering another without anything of the same type in between.
-
C.
hasNearbyFunction
Indicates that one entity has another entity located close by that serves a related or supportive function.
-
D.
hasNeighboringBuilding
Indicates that one building is located adjacent to or directly next to another building.
-
E.
hasNearbyEventType
Indicates that an event of a specified type occurs in close spatial or contextual proximity to a given reference entity or location.
- 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_69ca847e53a88190a60eed7e02257f10 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99487b4c819086e02e29e37b593f |
completed | April 1, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69ccd594d0ac8190a81bc11a3a538167 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:03 p.m.