Triple
T33367097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | municipality of Fribourg |
E854383
|
entity |
| Predicate | hasHistoricBridges |
P198173
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [municipality of Fribourg, hasHistoricBridges, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricBridges Context triple: [municipality of Fribourg, hasHistoricBridges, true]
-
A.
isHistoricBridgeOf
Indicates that a bridge has historical significance and serves or served as a notable crossing associated with a particular place or route.
-
B.
chronologicallyBridges
Indicates a temporal relationship where one event, period, or entity spans across and connects two or more distinct points or intervals in time.
-
C.
hasBridgeAndTrestleStructures
Indicates that the subject includes or features both bridge and trestle structural elements.
-
D.
isOldestSurvivingBridgeAcross
Indicates that a bridge is the most ancient still-existing bridge that spans a specified waterway, road, or gap.
-
E.
FourFamousAncientBridgesWith
Indicates a relationship where an entity is associated with a set or group of four notable and historically significant ancient bridges.
- 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_69f3496bda8c8190bfc8fade9d1b791c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69feced53a7c819098ec474fb7d514b0 |
completed | May 9, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69fecd9cd5288190aac8b4e04a7ee78e |
completed | May 9, 2026, 6:01 a.m. |
| PDg | Predicate description generation | batch_69feced436a48190b761db7df2d6b6bd |
completed | May 9, 2026, 6:06 a.m. |
Created at: May 1, 2026, 1:35 a.m.