Triple
T5762174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leidsegracht bridge over Prinsengracht |
E127120
|
entity |
| Predicate | inNetwork |
P66218
|
FINISHED |
| Object | Amsterdam canal bridges |
—
|
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: Amsterdam canal bridges | Statement: [Leidsegracht bridge over Prinsengracht, inNetwork, Amsterdam canal bridges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inNetwork Context triple: [Leidsegracht bridge over Prinsengracht, inNetwork, Amsterdam canal bridges]
-
A.
network
Indicates that one entity is connected to or interacts with another through a system of relationships, communication, or information exchange.
-
B.
basedOnNetwork
Indicates that something is determined, derived, or operates according to a particular network or network-related characteristics.
-
C.
isOnNetwork
Indicates that an entity is currently connected to, accessible through, or operating within a specified network.
-
D.
networkServed
Indicates that a network provides connectivity or services to a particular entity or set of entities.
-
E.
positionInNetwork
Indicates the specific role or location an entity occupies within a network’s structure or topology.
- 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_69c00833a3fc81908f4bc29ed011b7a6 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02939b22c81908f8354ab175d168d |
completed | March 22, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69c021cc68648190bb86d049ebe80f12 |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c028fec2bc819083f5dca6a8d9d435 |
completed | March 22, 2026, 5:38 p.m. |
Created at: March 22, 2026, 3:49 p.m.