Triple
T18334435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omega Sector |
E439231
|
entity |
| Predicate | agentCoverExample |
P109187
|
FINISHED |
| Object | computer salesman for Harry Tasker |
—
|
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: computer salesman for Harry Tasker | Statement: [Omega Sector, agentCoverExample, computer salesman for Harry Tasker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: agentCoverExample Context triple: [Omega Sector, agentCoverExample, computer salesman for Harry Tasker]
-
A.
usedCover
Indicates that one entity employed another entity as a protective or concealing cover in a given context.
-
B.
coverLocation
Indicates that one entity serves as a covering or protective layer positioned at or over a specific location of another entity.
-
C.
coverRole
chosen
Indicates that one entity temporarily assumes or fills the role, duties, or position normally held by another entity.
-
D.
eraCovered
Indicates that one entity temporally encompasses, includes, or spans the historical period or era associated with another entity.
-
E.
coversPerson
Indicates that one entity provides protection, insurance, or inclusion for a person under its scope or terms.
- 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_69d8b9175fec8190af865699b4e64d8c |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50ecc91148190aa820fcd466009ce |
completed | April 19, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_69e44fe91bc08190906518e1b120fcf0 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:36 a.m.