Triple
T8416338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oceania |
E198737
|
entity |
| Predicate | controlsPopulationThrough |
P82062
|
FINISHED |
| Object | fear |
—
|
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: fear | Statement: [Oceania, controlsPopulationThrough, fear]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlsPopulationThrough Context triple: [Oceania, controlsPopulationThrough, fear]
-
A.
proposesPopulationLimit
Indicates that an entity suggests or advocates setting a maximum allowable size for a population.
-
B.
governedPopulation
Indicates that one entity serves as the governing authority over the population of another entity.
-
C.
populationThreshold
Indicates that a population has reached, exceeded, or fallen below a specified numerical limit used as a critical or decision-making boundary.
-
D.
captivePopulation
Indicates that the entities are part of a population kept in captivity, such as in zoos, aquariums, or breeding facilities, rather than living in the wild.
-
E.
reducedPopulationOf
Indicates a relationship where one entity has caused a decrease in the size or number of individuals in a population of another entity.
- F. None of above. chosen
Provenance (4 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_69ca831201b481909e137936ef99ff11 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb84c5121081908efa3eca25406d3a |
completed | March 31, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69cb70d70ea081909c3dc1bd2ec14f85 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb77690720819099de1e22b84a9563 |
completed | March 31, 2026, 7:27 a.m. |
Created at: March 30, 2026, 6:06 p.m.