Triple
T30031162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 博斯腾湖 |
E763020
|
entity |
| Predicate | 成因类型 |
P54753
|
FINISHED |
| Object | 构造湖 |
—
|
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: 构造湖 | Statement: [博斯腾湖, 成因类型, 构造湖]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 成因类型 Context triple: [博斯腾湖, 成因类型, 构造湖]
-
A.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
B.
causesFeaturesIn
Indicates that one entity is responsible for producing, giving rise to, or bringing about specific characteristics or features in another entity.
-
C.
hasCauseOfFormation
Indicates that one entity is the cause, origin, or formative factor leading to the creation or development of another entity.
-
D.
causeStatus
Indicates that one entity brings about, initiates, or is responsible for a particular state or condition in another entity.
-
E.
primaryCauseCategory
chosen
Indicates the main type or classification of cause responsible for an outcome or event.
- 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_69f2246fb2b88190acff36bf7975c8f0 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f679afd2a88190856acb9e2d1f87d3 |
completed | May 2, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:50 p.m.