Triple
T35705626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Credit Dauphine |
E1031710
|
entity |
| Predicate | coverIdentityFor |
P193043
|
FINISHED |
| Object | covert organization |
—
|
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: covert organization | Statement: [Credit Dauphine, coverIdentityFor, covert organization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coverIdentityFor Context triple: [Credit Dauphine, coverIdentityFor, covert organization]
-
A.
coverIdentityCreatedBy
Indicates that a cover identity was created by a particular agent or entity.
-
B.
primaryCoverIdentity
chosen
Indicates that one entity serves as the main or principal cover identity used by another entity, typically for concealment or undercover purposes.
-
C.
coverUpBy
Indicates that one entity conceals, suppresses, or hides the actions, information, or wrongdoing associated with another entity.
-
D.
characterCoverIdentity
Indicates that one character uses another identity as a cover or disguise, typically concealing their true identity.
-
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_69f76e0d393c8190b6303c64408736db |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: May 3, 2026, 4:05 p.m.