Triple
T4621760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kasugayama Primeval Forest |
E101000
|
entity |
| Predicate | disturbanceLevel |
P57472
|
FINISHED |
| Object | largely undisturbed |
—
|
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: largely undisturbed | Statement: [Kasugayama Primeval Forest, disturbanceLevel, largely undisturbed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disturbanceLevel Context triple: [Kasugayama Primeval Forest, disturbanceLevel, largely undisturbed]
-
A.
noiseLevel
Indicates the intensity or amount of sound present in a given environment or from a specific source.
-
B.
affectedLevel
Indicates the degree or extent to which one entity is impacted or influenced by another entity or event.
-
C.
eraOfIncreasedIntensity
Indicates a period during which the level or strength of a particular activity, condition, or phenomenon becomes significantly higher than before.
-
D.
joyLevel
Indicates the degree or intensity of joy experienced or expressed by an entity.
-
E.
disruptsContinuityOf
Indicates that one entity interrupts, breaks, or otherwise prevents the ongoing, uninterrupted progression or sequence of another entity or process.
- F. None of above. chosen
Provenance (4 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_69bd43d0497c8190ac23c65c5804846a |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a0374308190aeaffc9d866a3742 |
completed | March 20, 2026, 2:30 p.m. |
| PD | Predicate disambiguation | batch_69bd5231db7c8190b38d4fdbad8bf842 |
completed | March 20, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69bd56b5f4648190834eafa666d53caa |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:12 p.m.