Triple
T34992466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ara River |
E1009429
|
entity |
| Predicate | hasHumanModificationLevel |
P139925
|
FINISHED |
| Object | low regulation |
—
|
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: low regulation | Statement: [Ara River, hasHumanModificationLevel, low regulation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHumanModificationLevel Context triple: [Ara River, hasHumanModificationLevel, low regulation]
-
A.
hasHumanModification
Indicates that an entity has been altered, influenced, or modified as a result of human activity or intervention.
-
B.
modificationLevel
chosen
Indicates the degree or extent to which something has been altered, adjusted, or changed from its original state.
-
C.
hasLevelHistory
Indicates that an entity is associated with a record or sequence of its past levels or states over time.
-
D.
isModifiedAs
Indicates that an entity has been altered or changed from its original state in some specified manner.
-
E.
showsModificationBy
Indicates that one entity displays or reveals the changes, alterations, or modifications that have been made by another entity.
- 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_69f76dca50dc8190b71f39defe186be8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.