Triple
T35766814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Armington |
E1034036
|
entity |
| Predicate | hasBoatingRegulation |
P172105
|
FINISHED |
| Object | subject to New Hampshire boating laws |
—
|
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: subject to New Hampshire boating laws | Statement: [Lake Armington, hasBoatingRegulation, subject to New Hampshire boating laws]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBoatingRegulation Context triple: [Lake Armington, hasBoatingRegulation, subject to New Hampshire boating laws]
-
A.
hasBoatingRestriction
chosen
Indicates that there is a rule or limitation governing the use or operation of boats in relation to a specified area, time, or condition.
-
B.
boatingAllowed
Indicates that operating or using boats is permitted in the specified area or context.
-
C.
hasBoatFacility
Indicates that an entity provides or is equipped with facilities or services specifically for boats.
-
D.
hasBoatLine
Indicates that one entity operates, owns, or is associated with a particular boat service or boat route line.
-
E.
canRideBoat
Indicates that an entity has the ability or permission to travel using a boat.
- 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_69f76e13edd081909101629aa829c4ad |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe031bc6208190860099aef72d8dcb |
completed | May 8, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69fe014c8b388190b5d4e0cb95ee2be5 |
completed | May 8, 2026, 3:29 p.m. |
Created at: May 3, 2026, 4:06 p.m.