Triple
T28877462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yichang counties |
E732310
|
entity |
| Predicate | areLocatedInRegion |
P9687
|
FINISHED |
| Object | Yangtze River basin |
E373511
|
NE 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: Yangtze River basin | Statement: [Yichang counties, areLocatedInRegion, Yangtze River basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areLocatedInRegion Context triple: [Yichang counties, areLocatedInRegion, Yangtze River basin]
-
A.
locatedInStateOrRegion
Indicates that one entity is geographically situated within the boundaries of a specified state or region.
-
B.
foundInRegion
chosen
Indicates that something is located within, occurs in, or is associated with a specific geographic or spatial region.
-
C.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
-
D.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
E.
usedInRegion
Indicates that something is utilized or applied within a specific geographic or administrative region.
- F. None of above.
Provenance (4 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65a4cb030819097b892710baa7d88 |
completed | May 2, 2026, 8:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a24d3fca02c81908d1a28feb2fdd480 |
completed | June 7, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 7:39 a.m.