Triple
T2379741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Willahelm |
E46281
|
entity |
| Predicate | traditionalUsageRegion |
P15483
|
FINISHED |
| Object | Germanic-speaking regions |
—
|
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: Germanic-speaking regions | Statement: [Willahelm, traditionalUsageRegion, Germanic-speaking regions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalUsageRegion Context triple: [Willahelm, traditionalUsageRegion, Germanic-speaking regions]
-
A.
hasTypicalUsageRegion
chosen
Indicates that something is most commonly or characteristically used within a particular geographic region.
-
B.
traditionalHousingRegion
Indicates the region where a group’s customary or historically established housing patterns are typically found.
-
C.
usedInRegion
Indicates that something is utilized or applied within a specific geographic or administrative region.
-
D.
traditionalRegionOfResidence
Indicates the customary or historically established geographic region where an entity (typically a person or group) resides or is considered to be from.
-
E.
traditionallyUsedBy
Indicates that something has been customarily or historically used by a particular person, group, or culture over time.
- 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_69a88a1554a48190a0180682bcf099be |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abc7b60c8c819080e4f682e4362a93 |
completed | March 7, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69abc59f73f08190924a36d7d475d8f4 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.