Triple
T37725796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vril-ya |
E939714
|
entity |
| Predicate | populationPolicy |
P14446
|
FINISHED |
| Object | strict control |
—
|
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: strict control | Statement: [Vril-ya, populationPolicy, strict control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: populationPolicy Context triple: [Vril-ya, populationPolicy, strict control]
-
A.
demographicPolicy
chosen
Indicates a relationship where an authority or organization establishes or applies rules and measures intended to influence the size, structure, or composition of a population.
-
B.
population
Indicates the total number of individuals living in or present within a specified area or group.
-
C.
populationIncrease
Indicates that the number of individuals in a population has grown over a specified period of time.
-
D.
populationFocus
Indicates that something is primarily directed toward, concerned with, or designed for a particular population or demographic group.
-
E.
populationCondition
Indicates the state, status, or characteristics of a population under certain specified conditions or constraints.
- 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_69f76edc208c8190bc8b9683f75e1024 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
Created at: May 3, 2026, 4:18 p.m.