Triple
T24753012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Firth of Forth basin |
E619198
|
entity |
| Predicate | hasBridgeCrossingEstuary |
P106621
|
FINISHED |
| Object | Forth Bridge |
—
|
NE NERFINISHED |
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: Forth Bridge | Statement: [Firth of Forth basin, hasBridgeCrossingEstuary, Forth Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBridgeCrossingEstuary Context triple: [Firth of Forth basin, hasBridgeCrossingEstuary, Forth Bridge]
-
A.
hasBridgeCrossings
chosen
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).
-
B.
hasBridgeTypeCrossing
Indicates that a bridge is characterized by a specific type of crossing it provides or supports.
-
C.
hasCanalCrossing
Indicates that one entity is connected to or traversed by another via a canal crossing, such as a bridge, aqueduct, or similar structure over a canal.
-
D.
hasEstuaryWith
Indicates that a river or watercourse flows into and forms an estuary with a particular body of water.
-
E.
hasEstuaryAt
Indicates that a river or watercourse flows into and meets a larger body of water (such as a sea, ocean, or lake) at a specific 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_69e2fabb349881908a13a212a0221a63 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410a25ab88190a72db43043c1f6ff |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:25 a.m.