Triple
T26473171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fox Point Hurricane Barrier |
E665954
|
entity |
| Predicate | floodControlType |
P25010
|
FINISHED |
| Object | tidal surge barrier |
—
|
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: tidal surge barrier | Statement: [Fox Point Hurricane Barrier, floodControlType, tidal surge barrier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floodControlType Context triple: [Fox Point Hurricane Barrier, floodControlType, tidal surge barrier]
-
A.
providesFloodControlFor
Indicates that one entity offers protection or mitigation against flooding for another entity or area.
-
B.
hasFloodControlStructure
chosen
Indicates that an entity possesses or is equipped with a structure designed to manage, control, or mitigate flooding.
-
C.
flowControl
Indicates a relationship where one entity regulates, directs, or manages the rate or sequence of another entity’s operations or movement.
-
D.
floodType
Indicates the specific kind or category of flooding involved in an event or situation.
-
E.
congestionControlAlgorithm
Indicates that one entity uses, implements, or is associated with a particular congestion control algorithm in managing network traffic.
- 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_69ee883f80dc819090e311b022b78e02 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f612ca2eac8190a1b97d0bacd9b20c |
completed | May 2, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 12:21 a.m.