Triple
T28133880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forth defences |
E714143
|
entity |
| Predicate | geographicFeatureDefended |
P170988
|
FINISHED |
| Object | Firth of Forth estuary |
—
|
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: Firth of Forth estuary | Statement: [Forth defences, geographicFeatureDefended, Firth of Forth estuary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicFeatureDefended Context triple: [Forth defences, geographicFeatureDefended, Firth of Forth estuary]
-
A.
fortressDefended
Indicates that a fortress is actively protected against threats or attacks by some defending force.
-
B.
fortificationTypeDefended
Indicates the specific type of fortification that an entity is responsible for defending or protecting.
-
C.
isFortificationGatewayOf
Indicates that a gateway or entrance structure serves as an access point or defensive portal belonging to a specific fortification.
-
D.
riverDefended
Indicates that a river is actively protected or guarded against threats, such as environmental damage, encroachment, or hostile actions.
-
E.
townDefendedBy
Indicates that a particular town is protected or guarded by a specified defending force or entity.
- 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_69efd6af156c81908f50c2cd7db0e1ef |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6984bb55c8190862eb8796868d188 |
completed | May 3, 2026, 12:35 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f6978ec27c8190a488e1f9c2566d38 |
completed | May 3, 2026, 12:32 a.m. |
Created at: April 27, 2026, 9:48 p.m.