Triple
T3221687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Bracciano |
E67524
|
entity |
| Predicate | motorboatRestrictions |
P33452
|
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: [Lake Bracciano, motorboatRestrictions, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: motorboatRestrictions Context triple: [Lake Bracciano, motorboatRestrictions, yes]
-
A.
hazardLevelForBoating
Indicates the degree of risk or danger that current conditions pose specifically for boating activities.
-
B.
hasShorelineUseRestrictions
Indicates that there are specific rules or limitations governing how the shoreline area associated with an entity may be used or developed.
-
C.
marineAttraction
Indicates a relationship where one entity serves as a point of interest or entertainment specifically related to marine life or the marine environment for another entity.
-
D.
marineProtectionStatus
Indicates the level or type of legal or regulatory protection applied to a marine area or resource.
-
E.
transportRestriction
chosen
Indicates that there are limitations, prohibitions, or special conditions governing the use of a particular mode or means of transportation between entities.
- 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_69ad858b8adc8190ad989712c87a476b |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adae1845408190b3eccd791231c69c |
completed | March 8, 2026, 5:12 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0bb6c48190a0659c67d40ee37c |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:08 p.m.