Triple
T10809323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antichrist |
E255054
|
entity |
| Predicate | typicalAttributes |
P5084
|
FINISHED |
| Object | deception |
—
|
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: deception | Statement: [Antichrist, typicalAttributes, deception]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAttributes Context triple: [Antichrist, typicalAttributes, deception]
-
A.
commonAttribute
Indicates that two or more entities share the same specified attribute or property.
-
B.
typicalFeatures
chosen
Indicates that the related entities are characteristic or commonly occurring features or attributes of something.
-
C.
typicalFields
Indicates the standard or commonly occurring attributes or data fields that are usually associated with an entity or record.
-
D.
commonAttributeSet
Indicates that the related entities share the same set of attributes or properties in common.
-
E.
typicalBase
Indicates that one entity serves as the standard or most representative base or foundation for another entity in typical or common cases.
- 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_69d6aa61c15c8190a1839550c56e75e1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d733b60c6481909b043565a65f996d |
completed | April 9, 2026, 5:05 a.m. |
| PD | Predicate disambiguation | batch_69d6f3188f00819094ee8d65b187a333 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:18 p.m.