Triple
T3330359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ilkenau |
E70017
|
entity |
| Predicate | nameUsedInContext |
P13305
|
FINISHED |
| Object | historical German documents |
—
|
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: historical German documents | Statement: [Ilkenau, nameUsedInContext, historical German documents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameUsedInContext Context triple: [Ilkenau, nameUsedInContext, historical German documents]
-
A.
nameUsedIn
chosen
Indicates that a particular name is employed or referenced within a specified context, work, or usage setting.
-
B.
nameUsedBy
Indicates that a particular name is employed or referenced by a specific entity.
-
C.
nameUsedFor
Indicates that a particular name is used to refer to or designate a given entity.
-
D.
namedInContextOf
Indicates that an entity is mentioned or identified specifically within a particular context, situation, or frame of reference.
-
E.
nameUsedToAvoid
Indicates that one entity uses a particular name or designation in order to avoid another entity or an unwanted situation involving that 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_69ad85a24f208190bcf83131bfed3521 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb171ee0881908642504ab0ac8329 |
completed | March 8, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69ada42a19348190a3862ce02451f4aa |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:12 p.m.