Triple
T37913907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vermont state boundary system |
E945758
|
entity |
| Predicate | hasBoundaryMarkerType |
P142064
|
FINISHED |
| Object | river thalweg |
—
|
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: river thalweg | Statement: [Vermont state boundary system, hasBoundaryMarkerType, river thalweg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBoundaryMarkerType Context triple: [Vermont state boundary system, hasBoundaryMarkerType, river thalweg]
-
A.
hasBorderMarkerType
chosen
Indicates that a border marker possesses or is classified by a specific type or category of border marker.
-
B.
hasBoundaryType
Indicates that one entity has a boundary characterized by a specific type or classification in relation to another entity or context.
-
C.
hasBoundaryCriterion
Indicates that something is associated with a specific rule or condition used to define or limit its boundary.
-
D.
hasBoundaryFeature
Indicates that a boundary (such as an edge, border, or limit) of one entity is characterized, marked, or defined by a specific feature or element.
-
E.
isBoundaryFor
Indicates that one entity serves as the limiting edge, border, or enclosing extent that defines the spatial or conceptual bounds of another entity.
- 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_69f76ef2ebd88190be5229f2621070b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe9b0276d48190b554fa22b043e6d8 |
completed | May 9, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69fe999692b081909921e1148d66f0ef |
completed | May 9, 2026, 2:19 a.m. |
Created at: May 3, 2026, 4:20 p.m.