Triple
T38582596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kul Tiras |
E932276
|
entity |
| Predicate | internalThreat |
P186194
|
FINISHED |
| Object | Drust |
—
|
NE NERFINISHED |
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: Drust | Statement: [Kul Tiras, internalThreat, Drust]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: internalThreat Context triple: [Kul Tiras, internalThreat, Drust]
-
A.
laterThreat
Indicates that one entity poses a threat to another at a time subsequent to some referenced or initial point.
-
B.
homeThreat
chosen
Indicates that an entity poses a danger, risk, or harmful presence to another entity within or directed toward its home or domestic environment.
-
C.
targetsThreat
Indicates that one entity is directing an action or focus specifically toward a perceived threat.
-
D.
systemThreatType
Indicates the category or nature of threat that a system poses or is exposed to.
-
E.
internalOutcome
Indicates an outcome or result that arises from within an entity, system, or process itself, rather than from external factors.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff0214d7348190904688376df99bce |
completed | May 9, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69feffd62fec8190a855922c8b3c57cf |
completed | May 9, 2026, 9:35 a.m. |
Created at: May 3, 2026, 4:32 p.m.