Triple
T34867652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NXIVM |
E1005056
|
entity |
| Predicate | hasSecretSubgroup |
P201365
|
FINISHED |
| Object | DOS |
—
|
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: DOS | Statement: [NXIVM, hasSecretSubgroup, DOS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecretSubgroup Context triple: [NXIVM, hasSecretSubgroup, DOS]
-
A.
hasSpecialSubgroup
Indicates that an entity includes or is associated with a particular subgroup that has distinctive or exceptional properties compared to its other subgroups.
-
B.
hasSecretLevel
Indicates that an entity is associated with a particular secrecy or security classification level.
-
C.
haveSubgroups
Indicates that an entity is organized into smaller constituent groups that are part of it.
-
D.
hasSubgroupStatus
Indicates that one group holds a specific status or classification as a subgroup within a larger group or organization.
-
E.
revealedAsSubgroupOf
Indicates that one group has been newly identified or exposed as being a subgroup or subset of another group.
- 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_69f76dbb678081909a247b9b5e1a73ac |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffed8912488190baa05f572e5b1b89 |
completed | May 10, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69ffed12a76c8190ad85c6ac869c72e9 |
completed | May 10, 2026, 2:27 a.m. |
| PDg | Predicate description generation | batch_69ffed884b908190b12422c790b1525e |
completed | May 10, 2026, 2:29 a.m. |
Created at: May 3, 2026, 4 p.m.