Triple
T27884255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amsterdam canal network |
E705180
|
entity |
| Predicate | numberOfBridgesApproximate |
P20771
|
FINISHED |
| Object | over 1500 |
—
|
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: over 1500 | Statement: [Amsterdam canal network, numberOfBridgesApproximate, over 1500]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfBridgesApproximate Context triple: [Amsterdam canal network, numberOfBridgesApproximate, over 1500]
-
A.
hasNumberOfMainBridges
Indicates the quantity of primary or main bridges associated with a given entity.
-
B.
hasNumberOfBridges
chosen
Indicates the quantitative relationship specifying how many bridges are associated with a given entity.
-
C.
riverCrossedByMaintainedBridges
Indicates that a river is spanned by one or more bridges that are actively maintained in usable condition.
-
D.
hasBridgeCrossings
Indicates that one entity has one or more bridge structures that span across or connect over another entity (such as a road, river, or area).
-
E.
numberOfSuspensionBridges
Indicates the count of suspension bridges associated with a given entity or within a specified context.
- 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_69ef96b39c448190a9b3aa6672a5168f |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69ff2636e2bc8190bba91eff91431c6e |
completed | May 9, 2026, 12:19 p.m. |
| PD | Predicate disambiguation | batch_69ff25c65be48190868480d94e1c4e89 |
completed | May 9, 2026, 12:17 p.m. |
Created at: April 27, 2026, 6:32 p.m.