Triple
T21960039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucas Burch |
E542300
|
entity |
| Predicate | attemptsToEvade |
P92600
|
FINISHED |
| Object | fatherhood responsibilities |
—
|
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: fatherhood responsibilities | Statement: [Lucas Burch, attemptsToEvade, fatherhood responsibilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attemptsToEvade Context triple: [Lucas Burch, attemptsToEvade, fatherhood responsibilities]
-
A.
escapeAttempt
Indicates an action where an entity tries to get away from confinement, control, or a restricting situation.
-
B.
seeksToAvoid
chosen
Indicates an entity’s intention or effort to stay away from, prevent, or not experience another entity or situation.
-
C.
triedToAvoid
Indicates an entity made an effort or took action to prevent contact with, involvement in, or the occurrence of another entity or situation.
-
D.
escapeMechanism
Indicates a means or method by which an entity avoids, evades, or breaks free from a threat, constraint, or controlling influence.
-
E.
canBeDodgedBy
Indicates that an action, effect, or attack is avoidable by a particular entity through dodging.
- 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_69e0c47fab1081908dc74a6545dbb051 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f12454a290819094d4b56547816e3f |
completed | April 28, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69e6f601f2188190893bcdde0cf58ad6 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 8 p.m.