Triple
T24599664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Casey |
E608786
|
entity |
| Predicate | worksUnderCoverAt |
P150188
|
FINISHED |
| Object | Buy More |
—
|
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: Buy More | Statement: [John Casey, worksUnderCoverAt, Buy More]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksUnderCoverAt Context triple: [John Casey, worksUnderCoverAt, Buy More]
-
A.
undercoverFor
chosen
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.
resultOfUndercoverWork
Indicates that something occurs as a consequence of, or is produced by, undercover investigative work.
-
D.
occupationInDisguise
Indicates that an entity’s true occupation is being concealed or performed under a false or hidden identity.
-
E.
workedUnder
Indicates that one entity was hierarchically subordinate to and performed work under the supervision or authority of another 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_69e2c4cf54248190af7b0c2d9ade9830 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6ca751c8190a040c10d701ecf3a |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:30 a.m.