Triple
T16732377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Attabad |
E406621
|
entity |
| Predicate | previouslyLocatedOn |
P55436
|
FINISHED |
| Object | original course of Hunza River |
—
|
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: original course of Hunza River | Statement: [Attabad, previouslyLocatedOn, original course of Hunza River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previouslyLocatedOn Context triple: [Attabad, previouslyLocatedOn, original course of Hunza River]
-
A.
formerlyLocatedOn
chosen
Indicates that an entity was once located on or situated upon another entity, but is no longer in that position.
-
B.
previouslyLocatedIn
Indicates that an entity was located in a particular place or region at some time in the past, but is not necessarily located there now.
-
C.
formerlyKnownLocationAs
Indicates that an entity was previously known or referred to by a different location name or designation.
-
D.
locatedAtFormer
Indicates that an entity is currently located at a place where another entity was previously located.
-
E.
previousLocationName
Indicates that one entity specifies the name of a location where another entity was situated or occurred before its current location.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e39c362bb88190921fab43d76c3ee8 |
completed | April 18, 2026, 2:59 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.