Triple
T30735956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N'Jobu |
E782553
|
entity |
| Predicate | operatesAsUndercoverAgentIn |
P180713
|
FINISHED |
| Object | United States |
—
|
NE NERFINISHED |
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: United States | Statement: [N'Jobu, operatesAsUndercoverAgentIn, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesAsUndercoverAgentIn Context triple: [N'Jobu, operatesAsUndercoverAgentIn, United States]
-
A.
undercoverOperationWith
Indicates that one entity is engaged in a covert or clandestine operation in collaboration with another entity.
-
B.
undercoverIn
chosen
Indicates that an entity is secretly operating within a group, organization, or environment under false or concealed identity.
-
C.
undercoverFor
Indicates that one entity is secretly acting on behalf of or within another entity, typically to gather information or carry out covert objectives without revealing their true affiliation.
-
D.
undercoverAgainst
Indicates that one entity is secretly acting in a covert or deceptive capacity directed against another entity.
-
E.
resultOfUndercoverWork
Indicates that something occurs as a consequence of, or is produced by, undercover investigative work.
- 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff779e3f0c8190a861f1e4000fd9d9 |
completed | May 9, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69ff77202638819086e4b9f9c0bc7b31 |
completed | May 9, 2026, 6:04 p.m. |
Created at: April 29, 2026, 8:37 p.m.