Triple
T29774567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sydkap Fiord region |
E755342
|
entity |
| Predicate | hasHumanActivityLevel |
P102394
|
FINISHED |
| Object | very low |
—
|
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: very low | Statement: [Sydkap Fiord region, hasHumanActivityLevel, very low]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHumanActivityLevel Context triple: [Sydkap Fiord region, hasHumanActivityLevel, very low]
-
A.
humanActivityLevel
chosen
Indicates the degree or intensity of activity or movement performed by a human over a given period or in a given context.
-
B.
hasHumanActivities
Indicates that certain human actions, behaviors, or practices are present, performed, or associated with a given entity.
-
C.
currentActivityLevel
Indicates the present intensity or degree of activity that an entity is engaged in at a given moment.
-
D.
has activity
Indicates that one entity performs, exhibits, or is engaged in a particular action, behavior, or process associated with another entity.
-
E.
evidenceOfActivity
Indicates that there is information or data supporting the occurrence or performance of a particular activity or action.
- 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_69f0ef878574819088c867fd1a5c8b86 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f67f7efc3c8190986d2d95b7a23729 |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 28, 2026, 8:45 p.m.