Triple
T28546456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Una National Park |
E722452
|
entity |
| Predicate | alsoIncludesRiver |
P165
|
FINISHED |
| Object | Unac River |
—
|
NE NERFINISHED |
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: Unac River | Statement: [Una National Park, alsoIncludesRiver, Unac River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoIncludesRiver Context triple: [Una National Park, alsoIncludesRiver, Unac River]
-
A.
hasRiver
chosen
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
B.
hasSettlementOnRiver
Indicates that a settlement is located on or directly adjacent to a specific river.
-
C.
betweenRiver
Indicates a spatial relationship where something is located in the area separating two rivers or lies in the intermediate region defined by them.
-
D.
hasFictionalRiver
Indicates that an entity includes, features, or is associated with a river that is fictional rather than real.
-
E.
locatedInRiverArea
Indicates that one entity is situated within the geographic area occupied by, adjacent to, or directly associated with a particular river.
- 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_69f01a5e42348190b1ffbca26e739c84 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6500e19f481908a1b35ae8b149236 |
completed | May 2, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:39 a.m.