Triple
T34640223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enchanted River |
E889534
|
entity |
| Predicate | travelAdvice |
P71489
|
FINISHED |
| Object | water should not be drunk |
—
|
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: water should not be drunk | Statement: [Enchanted River, travelAdvice, water should not be drunk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: travelAdvice Context triple: [Enchanted River, travelAdvice, water should not be drunk]
-
A.
travelAdvisory
chosen
Indicates that one authority issues guidance or warnings to others about safety, risks, or conditions related to traveling to a particular place.
-
B.
travelZone
Indicates a relationship where an entity is located in, moves within, or is permitted to move within a specified geographic or regulatory area.
-
C.
travelsAbroad
Indicates that an entity goes to or spends time in a foreign country outside its usual nation of residence.
-
D.
travelScope
Indicates the extent or range within which travel is allowed, intended, or applicable for an entity or activity.
-
E.
travelRequirement
Indicates that a certain amount or type of travel is necessary for participating in or fulfilling the associated activity, role, or arrangement.
- 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_69f349d724848190b63ad3407e0006d9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f73397e5488190a9cdce98a0ac0383 |
completed | May 3, 2026, 11:38 a.m. |
| PD | Predicate disambiguation | batch_69f732f3ad248190b4bcbf589d000f0d |
completed | May 3, 2026, 11:35 a.m. |
Created at: May 1, 2026, 2:04 a.m.