Triple
T28382157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lubyanka Criminal Group |
E718915
|
entity |
| Predicate | authorDescribes |
P180782
|
FINISHED |
| Object | internal operations of the FSB |
—
|
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: internal operations of the FSB | Statement: [Lubyanka Criminal Group, authorDescribes, internal operations of the FSB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorDescribes Context triple: [Lubyanka Criminal Group, authorDescribes, internal operations of the FSB]
-
A.
authorDescribedIn
Indicates that information about an author is provided or discussed within a particular document or source.
-
B.
authorOfDescription
Indicates that an entity is the creator or writer of a particular description or explanatory text about something.
-
C.
authorDescription
Indicates that a person provides a textual description or biographical summary of an author.
-
D.
authorsDescribedBy
Indicates that an entity serves as a descriptive account or characterization of one or more authors.
-
E.
authorName
Indicates the name associated with the person or entity that authored a given work or resource.
- 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
| PDg | Predicate description generation | batch_69f7516c538481908c6e55cf76add098 |
completed | May 3, 2026, 1:45 p.m. |
Created at: April 28, 2026, 1:07 a.m.