Triple
T19876470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enola |
E477649
|
entity |
| Predicate | pursuedBecauseOf |
P69059
|
FINISHED |
| Object | tattoo map to Dryland |
—
|
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: tattoo map to Dryland | Statement: [Enola, pursuedBecauseOf, tattoo map to Dryland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pursuedBecauseOf Context triple: [Enola, pursuedBecauseOf, tattoo map to Dryland]
-
A.
pursuedForCrime
Indicates that an entity is being actively sought or chased by authorities or others because of an alleged or committed crime.
-
B.
investigatedFor
Indicates that an entity is the subject of an investigation concerning a suspected involvement in another entity (typically a crime, incident, or wrongdoing).
-
C.
isSoughtBy
Indicates that one entity is actively being searched for, pursued, or desired by another entity.
-
D.
targetedBecauseOf
chosen
Indicates that one entity is made a target of an action, harm, or scrutiny specifically due to possessing a particular attribute, identity, or characteristic.
-
E.
pursuesCrimeType
Indicates that an entity (such as a law enforcement body or individual) actively investigates, targets, or prosecutes a specified type of crime.
- 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_69d8e51f32b08190b3687f4f60353250 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e658dbdb648190b423865e7994a8fe |
completed | April 20, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_69e537e8c4e481909fe95d795b4864e7 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:52 p.m.