Triple
T33703246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OWCA |
E863514
|
entity |
| Predicate | coverIdentityPolicy |
P47547
|
FINISHED |
| Object | agents must maintain secret identities |
—
|
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: agents must maintain secret identities | Statement: [OWCA, coverIdentityPolicy, agents must maintain secret identities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coverIdentityPolicy Context triple: [OWCA, coverIdentityPolicy, agents must maintain secret identities]
-
A.
coverIdentityCreatedBy
Indicates that a cover identity was created by a particular agent or entity.
-
B.
coverIdentities
chosen
Indicates that one entity conceals, masks, or protects the true identities of one or more other entities.
-
C.
coverStatus
Indicates the current state or condition of coverage that applies to an entity, such as whether coverage is active, pending, expired, or otherwise classified.
-
D.
coverUpBy
Indicates that one entity conceals, suppresses, or hides the actions, information, or wrongdoing associated with another entity.
-
E.
coverVersionBy
Indicates that one creative work is a cover version performed or produced by a particular artist or entity.
- 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_69f3498844608190bb8f9b14908d2510 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 1, 2026, 1:43 a.m.