Triple
T38447622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nogrod |
E906681
|
entity |
| Predicate | inhabitantEthnicity |
P159087
|
FINISHED |
| Object | Longbeards and related Dwarven clans |
—
|
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: Longbeards and related Dwarven clans | Statement: [Nogrod, inhabitantEthnicity, Longbeards and related Dwarven clans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inhabitantEthnicity Context triple: [Nogrod, inhabitantEthnicity, Longbeards and related Dwarven clans]
-
A.
holderEthnicity
Indicates the ethnic background or group to which the holder of something (e.g., a document, account, or item) belongs.
-
B.
sharesEthnicity
Indicates that two entities belong to the same ethnic group or share the same ethnic background.
-
C.
hostEthnicity
Indicates the ethnic background or ethnicity of the host in the relationship or context described.
-
D.
nearEthnicGroup
Indicates that one entity is located geographically close to an ethnic group.
-
E.
populationEthnicGroup
chosen
Indicates that a specified ethnic group constitutes part or all of the population of a given place or community.
- 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_69f76e72878c8190a692836c8b01b58b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcce7afcd08190906cc3801152656a |
completed | May 7, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69fcccf140ec8190862d53388a5f40d7 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.