Triple
T33324206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ys |
E853220
|
entity |
| Predicate | hasSeaDike |
P27578
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Ys, hasSeaDike, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeaDike Context triple: [Ys, hasSeaDike, yes]
-
A.
partlyDikedSince
Indicates that an entity has been partially protected or enclosed by dikes starting from a specified point in time.
-
B.
DikeRepresents
Indicates that one entity (typically a person or organization) serves as the legal representative or advocate for another entity in matters concerning a dike or flood-defense structure.
-
C.
dikeBreaches
Indicates that a dike fails or ruptures, allowing water to break through its barrier.
-
D.
hasEmbankment
chosen
Indicates that one entity possesses or is characterized by an embankment, such as a raised structure built to contain, support, or protect against water or terrain.
-
E.
hasMarinaOrStaithe
Indicates that a place includes or is associated with a marina or staithe (a landing stage or mooring area for boats).
- 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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff7ae5d088819089aa3b6360b6b749 |
completed | May 9, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69ff7a4df6488190bf60d675b36b1d6d |
completed | May 9, 2026, 6:17 p.m. |
Created at: May 1, 2026, 1:33 a.m.