Triple
T18401198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPECTRE |
E449998
|
entity |
| Predicate | usesFrontOrganizations |
P33645
|
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: [SPECTRE, usesFrontOrganizations, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFrontOrganizations Context triple: [SPECTRE, usesFrontOrganizations, true]
-
A.
hasFrontOrganization
Indicates that an entity is represented, covered, or operated through another entity that serves as its front or façade organization.
-
B.
usesOrganization
Indicates that one entity makes use of, relies on, or operates through a particular organization to perform its functions or activities.
-
C.
usesCoverOrganizations
chosen
Indicates that an entity operates through or makes use of front or intermediary organizations to conceal its true identity, role, or activities.
-
D.
includesOrganization
Indicates that one entity contains, encompasses, or has within it the specified organization as a component, member, or part.
-
E.
hasOrganizationFor
Indicates that one entity possesses, is associated with, or is responsible for a particular organization in relation to some context or purpose.
- 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_69d8b9fab8a8819086a9ddc0871715e0 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e5195185b08190bd3b5471cdc047b0 |
completed | April 19, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e44ff1f92c8190afbb8e85d12bf2a9 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:46 a.m.