Triple
T28738390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nick Torres |
E730864
|
entity |
| Predicate | undercoverExpertise |
P180028
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Nick Torres, undercoverExpertise, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: undercoverExpertise Context triple: [Nick Torres, undercoverExpertise, yes]
-
A.
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.
-
B.
undercoverAgainst
Indicates that one entity is secretly acting in a covert or deceptive capacity directed against another entity.
-
C.
hidesInPlainSight
Indicates that an entity conceals itself or its true nature while remaining visible or seemingly ordinary within its surroundings.
-
D.
resultOfUndercoverWork
Indicates that something occurs as a consequence of, or is produced by, undercover investigative work.
-
E.
secretlyInformed
Indicates that one entity provided information to another in a concealed or confidential manner, without the knowledge of others.
- F. None of above. chosen
Provenance (4 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_69f043eae0908190b28ce314686247d7 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
| PDg | Predicate description generation | batch_69f730890a008190a882f7828f1c9162 |
completed | May 3, 2026, 11:24 a.m. |
Created at: April 28, 2026, 6:01 a.m.