Triple
T20983215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Entity's Realm |
E516819
|
entity |
| Predicate | trapFor |
P63987
|
FINISHED |
| Object | Survivors taken by The Entity |
—
|
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: Survivors taken by The Entity | Statement: [The Entity's Realm, trapFor, Survivors taken by The Entity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trapFor Context triple: [The Entity's Realm, trapFor, Survivors taken by The Entity]
-
A.
trapLocation
Indicates the specific place or area where a trap is set, located, or expected to be found.
-
B.
trap
chosen
Indicates that an entity captures, confines, or ensnares another entity, typically preventing its escape or movement.
-
C.
trapTrigger
Indicates that an entity activates or sets off a trap in the environment.
-
D.
trapType
Indicates the specific kind or category of trap associated with an entity or situation.
-
E.
caughtBetween
Indicates being simultaneously subject to opposing forces, demands, or sides, unable to fully align with or escape either.
- 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_69e0b4ffac148190bbade9f0eceb660b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fbe03244819097630333e70c4e88 |
completed | April 21, 2026, 4:24 a.m. |
| PD | Predicate disambiguation | batch_69e5dbe6976081908abd4e9c8734bae9 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:48 p.m.