Triple
T9745882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hercynian Forest |
E236305
|
entity |
| Predicate | modernRemnantsInclude |
P89387
|
FINISHED |
| Object | Harz Mountains forests |
—
|
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: Harz Mountains forests | Statement: [Hercynian Forest, modernRemnantsInclude, Harz Mountains forests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernRemnantsInclude Context triple: [Hercynian Forest, modernRemnantsInclude, Harz Mountains forests]
-
A.
remnants
Indicates that parts or traces of something remain after the main portion has been removed, used, or destroyed.
-
B.
remnantsInclude
chosen
Indicates that the remaining parts or leftovers of one entity contain or consist of another entity.
-
C.
modernBase
Indicates that one entity serves as the contemporary or current foundational basis or reference point for another entity.
-
D.
modernAccess
Indicates that an entity has contemporary, up-to-date means or methods of accessing or interacting with another entity or resource.
-
E.
modernRevivalIn
Indicates that something has experienced a renewed or modern resurgence, popularity, or reinterpretation within a specified place, context, or period.
- 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_69ca84d3e24481908a476e2231123cf9 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9f65ad788190b68d731b6f516d93 |
completed | April 1, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69cd03cc128c81908b84ef224f858b4e |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:23 p.m.