Triple
T38570598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zoltan Karpathy |
E929256
|
entity |
| Predicate | attemptsToExpose |
P173280
|
FINISHED |
| Object | Eliza Doolittle |
—
|
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: Eliza Doolittle | Statement: [Zoltan Karpathy, attemptsToExpose, Eliza Doolittle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attemptsToExpose Context triple: [Zoltan Karpathy, attemptsToExpose, Eliza Doolittle]
-
A.
triesToExpose
chosen
Indicates an attempt by one entity to reveal, uncover, or make known information, intentions, or characteristics of another entity or situation.
-
B.
exposesTo
Indicates that one entity subjects another entity to contact with or influence from something, typically involving risk, effect, or experience.
-
C.
exposes
Indicates making something visible, known, or vulnerable by removing cover, concealment, or protection.
-
D.
exposedThrough
Indicates that something becomes revealed, accessible, or affected as a result of passing through or being subjected to another thing or medium.
-
E.
exposedDuring
Indicates that something becomes visible, accessible, or subject to influence specifically within a given time period, event, or contextual interval.
- 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_69f76ebd2248819083978362d81fa35e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.