Triple
T19694552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Locusts |
E472920
|
entity |
| Predicate | comparesHumanColonizationTo |
P136951
|
FINISHED |
| Object | a swarm of locusts |
—
|
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: a swarm of locusts | Statement: [The Locusts, comparesHumanColonizationTo, a swarm of locusts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comparesHumanColonizationTo Context triple: [The Locusts, comparesHumanColonizationTo, a swarm of locusts]
-
A.
wasLaterColonizedBy
Indicates that one entity became a colony of another entity at a later point in time than some referenced event or colonization.
-
B.
numberOfColonies
Indicates the count of distinct colonies associated with or possessed by a given entity.
-
C.
colonizationCenturyBC
Indicates the century before the Common Era in which a colonization event or process took place.
-
D.
colonizingPeople
Indicates that one group of people establishes control over and settles in the territory of another group.
-
E.
regionOfColonization
Indicates the geographic area or territory where a colonizing entity establishes and exercises colonial control.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6421385e88190b22b12ab3d851dea |
completed | April 20, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:46 p.m.