Triple
T38634364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No Russian |
E937538
|
entity |
| Predicate | playerCoverIdentity |
P114813
|
FINISHED |
| Object | undercover terrorist operative |
—
|
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: undercover terrorist operative | Statement: [No Russian, playerCoverIdentity, undercover terrorist operative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerCoverIdentity Context triple: [No Russian, playerCoverIdentity, undercover terrorist operative]
-
A.
characterCoverIdentity
chosen
Indicates that one character uses another identity as a cover or disguise, typically concealing their true identity.
-
B.
primaryCoverIdentity
Indicates that one entity serves as the main or principal cover identity used by another entity, typically for concealment or undercover purposes.
-
C.
appearsInIdentity
Indicates that an entity is featured, referenced, or plays a role within a particular identity or identity-related context.
-
D.
coverIdentityCreatedBy
Indicates that a cover identity was created by a particular agent or entity.
-
E.
coverIdentityFather
Indicates that one entity conceals, disguises, or assumes the identity of another entity who is the father.
- 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
Created at: May 3, 2026, 4:32 p.m.