Triple
T4640930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Barrington, Illinois |
E101651
|
entity |
| Predicate | hasBoatAccess |
P31589
|
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: [Port Barrington, Illinois, hasBoatAccess, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBoatAccess Context triple: [Port Barrington, Illinois, hasBoatAccess, yes]
-
A.
hasSeaAccess
Indicates that an entity has direct access to the sea, typically via a coastline, port, or navigable waterway connected to the sea.
-
B.
waterwayAccess
chosen
Indicates that one location has direct access to a waterway (such as a river, canal, or sea route) that can be used for transport, navigation, or related activities.
-
C.
hasBoat
Indicates that one entity possesses, owns, or has control over a boat.
-
D.
boatingAllowed
Indicates that operating or using boats is permitted in the specified area or context.
-
E.
hasBoatLine
Indicates that one entity operates, owns, or is associated with a particular boat service or boat route line.
- 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_69bd43d3bc7c81908f81fcf380476b0f |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a8fbd2c8190b593cd46ce8dfe0f |
completed | March 20, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69bd5234d24c819095c79890b70eff9a |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:14 p.m.