Triple
T31712386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marty Wolf |
E809360
|
entity |
| Predicate | stealsWorkTitled |
P172453
|
FINISHED |
| Object | Big Fat Liar (school essay) |
—
|
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: Big Fat Liar (school essay) | Statement: [Marty Wolf, stealsWorkTitled, Big Fat Liar (school essay)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stealsWorkTitled Context triple: [Marty Wolf, stealsWorkTitled, Big Fat Liar (school essay)]
-
A.
hasTitleWork
Indicates that an entity is associated with a specific work by its title (i.e., the entity has or bears that work’s title).
-
B.
createdForWorkByTitle
Indicates that a work was created specifically for, or commissioned by, a person or entity identified by their title.
-
C.
tookTitleFrom
Indicates that one entity adopted or derived its title, name, or designation from another entity.
-
D.
hasWorkingTitle
Indicates that an entity is associated with a provisional or temporary title used during its development or production.
-
E.
claimedTitle
Indicates that an entity asserts or declares possession of a particular title or rank.
- F. None of above. chosen
Provenance (4 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_69f348df4e048190a4a5a9932ada78d6 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abe15d5c81909ccf4ce37f78bc43 |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aaf31a548190b2f792ff4b8c002a |
completed | May 3, 2026, 1:54 a.m. |
Created at: April 30, 2026, 11:16 p.m.