Triple
T35345876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myles Standish State Forest pond system |
E1020735
|
entity |
| Predicate | typicalBoating |
P46319
|
FINISHED |
| Object | non-motorized boats |
—
|
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: non-motorized boats | Statement: [Myles Standish State Forest pond system, typicalBoating, non-motorized boats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBoating Context triple: [Myles Standish State Forest pond system, typicalBoating, non-motorized boats]
-
A.
boatRole
Indicates the specific function, duty, or position an entity has in relation to a boat within a given context.
-
B.
boatingAllowed
chosen
Indicates that operating or using boats is permitted in the specified area or context.
-
C.
boatLaunch
Indicates the action or event of setting a boat into the water from land or a structure so it can begin operating or traveling.
-
D.
canRideBoat
Indicates that an entity has the ability or permission to travel using a boat.
-
E.
usesCrewedBoats
Indicates that an entity performs an activity or operation by employing boats that are crewed by people.
- 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_69f76decd95c8190ae428f6a19d535de |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.