Triple
T28025866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort H. G. Wright |
E708120
|
entity |
| Predicate | waterBodyGuarded |
P139773
|
FINISHED |
| Object | Long Island Sound |
—
|
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: Long Island Sound | Statement: [Fort H. G. Wright, waterBodyGuarded, Long Island Sound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterBodyGuarded Context triple: [Fort H. G. Wright, waterBodyGuarded, Long Island Sound]
-
A.
hasShelteredWaters
chosen
Indicates that one location provides protected or calm waters for another location or activity, shielding it from rough or open conditions.
-
B.
navigatesWaterBody
Indicates that an entity moves through or across a body of water as a means of travel or operation.
-
C.
locatedInWaterBodyType
Indicates that an entity is situated within or on a body of water of a specified type (e.g., lake, river, ocean).
-
D.
waterBodyView
Indicates that an entity has a visual outlook or view onto a body of water, such as a lake, river, or ocean.
-
E.
touchesBodyOfWater
Indicates that one entity is in direct physical contact with the surface or boundary of a body of water.
- 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_69ef9b6bdd9c8190bb3a574a03774ad1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 27, 2026, 8:12 p.m.