Triple
T36760942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gonnhirrim |
E908197
|
entity |
| Predicate | usedAsCollectiveNameFor |
P127829
|
FINISHED |
| Object | All Dwarven kindreds |
—
|
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: All Dwarven kindreds | Statement: [Gonnhirrim, usedAsCollectiveNameFor, All Dwarven kindreds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsCollectiveNameFor Context triple: [Gonnhirrim, usedAsCollectiveNameFor, All Dwarven kindreds]
-
A.
usedCollectiveName
Indicates that a group of entities is referred to by a shared collective name.
-
B.
collectiveNameForm
Indicates that one entity serves as the collective or group name form used to refer to multiple members of another entity or class.
-
C.
collectivelyKnownAs
Indicates that multiple entities are referred to together under a single shared name or designation.
-
D.
collectiveTermUsed
chosen
Indicates that one entity is used as a collective term referring to a group or class of other entities.
-
E.
oftenUsedAsNameFor
Indicates that something frequently serves as a name or designation for another 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_69f76e779bec8190be0e1f87a131e0f4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fedec693b08190b0f8bfdb921e0766 |
completed | May 9, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69fede16c1d48190a20d8a9c5722c307 |
completed | May 9, 2026, 7:11 a.m. |
Created at: May 3, 2026, 4:12 p.m.