Triple
T19694563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Locusts |
E472920
|
entity |
| Predicate | portraysHumansAs |
P109101
|
FINISHED |
| Object | invading force |
—
|
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: invading force | Statement: [The Locusts, portraysHumansAs, invading force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portraysHumansAs Context triple: [The Locusts, portraysHumansAs, invading force]
-
A.
portraysPersonAs
Indicates that one entity represents, depicts, or characterizes another person in a particular way or role.
-
B.
portrayalIntendedAs
Indicates that one entity is meant to represent, depict, or stand in for another entity in an intentional portrayal.
-
C.
treatsHumansAs
chosen
Indicates how one entity regards or behaves toward humans, characterizing them in a particular way (e.g., as equals, tools, resources, or threats).
-
D.
portraysVampiresAs
Indicates how something represents or depicts vampires, especially in terms of their nature, traits, or role.
-
E.
portraysMainCharacter
Indicates that one entity depicts or represents another entity as the primary or central character in a work or narrative.
- 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_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. |
Created at: April 10, 2026, 1:46 p.m.