Triple
T33598513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jadis |
E860643
|
entity |
| Predicate | statusInWorldBeyond |
P198836
|
FINISHED |
| Object | antagonist |
—
|
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: antagonist | Statement: [Jadis, statusInWorldBeyond, antagonist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInWorldBeyond Context triple: [Jadis, statusInWorldBeyond, antagonist]
-
A.
statusInRevelation
Indicates the role, condition, or standing that an entity holds within the context of a particular revelation or revealed message.
-
B.
statusInAliens
Indicates the status or condition an entity holds within the context of aliens or an alien-related domain.
-
C.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
-
D.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
E.
statusInNippur
Indicates the social, legal, or administrative standing an entity holds specifically within the city or jurisdiction of Nippur.
- 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_69f3497f35908190a2e9bbb9b96c7a3f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff0d80c0dc81909fbd12285c7a45c0 |
completed | May 9, 2026, 10:33 a.m. |
| PD | Predicate disambiguation | batch_69ff0cd03e78819094895058f925fbfa |
completed | May 9, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69ff0d800ee88190835e233d9e846cdb |
completed | May 9, 2026, 10:33 a.m. |
Created at: May 1, 2026, 1:41 a.m.