Triple
T33632394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jessica Hyde |
E861600
|
entity |
| Predicate | pursuedFor |
P19739
|
FINISHED |
| Object | secrets she holds |
—
|
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: secrets she holds | Statement: [Jessica Hyde, pursuedFor, secrets she holds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pursuedFor Context triple: [Jessica Hyde, pursuedFor, secrets she holds]
-
A.
pursuedForCrime
Indicates that an entity is being actively sought or chased by authorities or others because of an alleged or committed crime.
-
B.
symbolicallyPursuedBy
Indicates that one entity is the target of another entity’s pursuit or quest in a figurative, metaphorical, or symbolic sense rather than a literal chase.
-
C.
isSoughtBy
chosen
Indicates that one entity is actively being searched for, pursued, or desired by another entity.
-
D.
claimedToPursue
Indicates that an entity has stated or asserted an intention to pursue another entity, goal, or course of action.
-
E.
partialPursuer
Indicates that one entity is attempting to pursue or chase another, but only to a limited, incomplete, or non-exclusive extent.
- 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_69f34981c54c81909b33c3fa2208a52d |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:41 a.m.