Triple
T1954243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rivanna River near Charlottesville |
E42228
|
entity |
| Predicate | hasAccessPointType |
P2836
|
FINISHED |
| Object | public boat launch |
—
|
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: public boat launch | Statement: [Rivanna River near Charlottesville, hasAccessPointType, public boat launch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccessPointType Context triple: [Rivanna River near Charlottesville, hasAccessPointType, public boat launch]
-
A.
hasServiceType
Indicates that an entity is associated with or categorized by a particular type of service.
-
B.
hasAcquisitionType
Indicates the specific kind or category of acquisition relationship that exists between one entity acquiring another.
-
C.
hasFacilityType
chosen
Indicates that an entity possesses or is associated with a specific type or category of facility.
-
D.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
E.
hasActivityType
Indicates the specific kind or category of activity associated with an entity or event.
- 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_69a8870eea088190a38781990812a9bc |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb351c148819080173c09876e814a |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abaff3eda88190b643994cb4dfb8df |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.