Triple
T28389402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 朝天门 |
E719108
|
entity |
| Predicate | 位于河流交汇处 |
P11842
|
FINISHED |
| Object | 长江 |
—
|
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: 长江 | Statement: [朝天门, 位于河流交汇处, 长江]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 位于河流交汇处 Context triple: [朝天门, 位于河流交汇处, 长江]
-
A.
locatedBetweenRivers
Indicates that something is situated in the area or region bounded or flanked by two rivers.
-
B.
locatedBetweenRiver
Indicates that an entity is situated in the area or region between two segments or banks of a river, or between two rivers.
-
C.
locatedAtConfluenceOf
chosen
Indicates that something is situated at the meeting point where two or more bodies of water or similar flowing features join together.
-
D.
riverConfluence
Indicates the location or relationship where two or more rivers or streams join and merge into a single watercourse.
-
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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64ceb933081909992f16507b0e667 |
completed | May 2, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 1:12 a.m.