Triple
T30056844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Superman villains |
E763755
|
entity |
| Predicate | oftenThreaten |
P181754
|
FINISHED |
| Object | Metropolis |
—
|
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: Metropolis | Statement: [Superman villains, oftenThreaten, Metropolis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenThreaten Context triple: [Superman villains, oftenThreaten, Metropolis]
-
A.
threat
Indicates a relationship where one entity expresses or poses potential harm, danger, or negative consequences toward another entity.
-
B.
threatenedUseOf
Indicates a situation where one entity has expressed or implied an intention to use force, harm, or coercive action against another entity.
-
C.
threatTypeEngaged
Indicates that an entity has actively engaged with or responded to a specific type of threat.
-
D.
threatType
Indicates the specific category or nature of a threat that one entity poses or represents in relation to another.
-
E.
usesIntimidationMethods
Indicates that an entity employs threats, coercion, or fear-based tactics to influence or control another entity.
- 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_69f224716378819087a722e487832b70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7824dc3f0819092a5102895b4a478 |
completed | May 3, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f7817c79e081908e685c48165e086b |
completed | May 3, 2026, 5:10 p.m. |
Created at: April 29, 2026, 6:56 p.m.