Triple
T6058754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plateau culture area |
E134978
|
entity |
| Predicate | notableEnvironment |
P47689
|
FINISHED |
| Object | river valleys |
—
|
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: river valleys | Statement: [Plateau culture area, notableEnvironment, river valleys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEnvironment Context triple: [Plateau culture area, notableEnvironment, river valleys]
-
A.
notableSystem
Indicates that a system is recognized as significant, prominent, or noteworthy in a particular context or domain.
-
B.
notableBase
Indicates that a particular location serves as a significant or distinguished base or headquarters for an entity.
-
C.
notableEnclave
Indicates that one place is a distinct, noteworthy enclave located within or surrounded by another area or community.
-
D.
notableSetting
chosen
Indicates that a particular place or environment is especially significant or prominent as the context in which an entity is situated or occurs.
-
E.
notableDuring
Indicates that something was especially prominent, active, or significant during a particular time period 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_69c00878d06881909ee78e88913bf890 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0570e64408190ae7a2504f63bb58a |
completed | March 22, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69c049edc6f0819092ca620d9073ad26 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:10 p.m.