Triple
T37204333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TNT: Evilution |
E922125
|
entity |
| Predicate | hasSecretLevels |
P202374
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [TNT: Evilution, hasSecretLevels, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecretLevels Context triple: [TNT: Evilution, hasSecretLevels, true]
-
A.
hasSecretLevel
Indicates that an entity is associated with a particular secrecy or security classification level.
-
B.
hasSecretArea
Indicates that an entity contains or is associated with a hidden or restricted area not normally accessible or visible.
-
C.
hasTypeOfSecrecy
Indicates that something is associated with a particular kind or level of secrecy.
-
D.
hasMultipleLevels
Indicates that something is organized into more than one hierarchical or structural level.
-
E.
securityLevelsInclude
Indicates that one entity’s defined security levels contain or encompass the security levels of 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_69f76ea4849481909b4a3073efb0114c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00776c4ebc8190899005fda34234d5 |
completed | May 10, 2026, 12:17 p.m. |
| PD | Predicate disambiguation | batch_6a0076f8a4c4819093ed577e67aa38f9 |
completed | May 10, 2026, 12:15 p.m. |
| PDg | Predicate description generation | batch_6a00776b69908190a431a48cc5e7dba9 |
completed | May 10, 2026, 12:17 p.m. |
Created at: May 3, 2026, 4:15 p.m.