Triple
T36054670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parselmouths |
E1042909
|
entity |
| Predicate | inWorldRarityEstimate |
P167372
|
FINISHED |
| Object | very few individuals per generation |
—
|
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: very few individuals per generation | Statement: [Parselmouths, inWorldRarityEstimate, very few individuals per generation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inWorldRarityEstimate Context triple: [Parselmouths, inWorldRarityEstimate, very few individuals per generation]
-
A.
inUniverseRarity
chosen
Indicates how rare or uncommon something is within the context of a specific fictional or defined universe.
-
B.
rarity
Indicates how uncommon or infrequently an entity or event occurs relative to others in a given context.
-
C.
instrumentRarity
Indicates how uncommon or scarce an instrument is relative to others.
-
D.
isCollectible
Indicates that an item can be gathered, acquired, or kept, typically as part of a set or collection.
-
E.
coinageRarity
Indicates the relative scarcity or commonness of a particular coinage within its issuing context.
- 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_69f76e2f09448190b0486d5ecad5e243 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b2c771108190adeec151daad5dab |
completed | May 3, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.