Triple
T38498418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yente |
E919757
|
entity |
| Predicate | associatedWithBookWriter |
P84740
|
FINISHED |
| Object | Joseph Stein |
E268004
|
NE 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: Joseph Stein | Statement: [Yente, associatedWithBookWriter, Joseph Stein]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithBookWriter Context triple: [Yente, associatedWithBookWriter, Joseph Stein]
-
A.
associatedWithAuthorWork
Indicates a relationship where an author is connected to a work they created, contributed to, or are otherwise credited for.
-
B.
associatedWithAuthorRole
chosen
Indicates that an entity is connected to another entity specifically in the capacity or role of an author.
-
C.
placeAssociatedWithAuthor
Indicates a relationship where a place is connected to an author, such as by birth, residence, work, or significant activity.
-
D.
authoredWith
Indicates that two or more entities jointly created or wrote a work together.
-
E.
workOfAuthorOf
Indicates that one entity is a work (such as a book, article, or artwork) created by the author associated with another entity.
- F. None of above.
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_69f76e9ddd4481908f8c04439d848f9d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41d6558f188190b7b780b83725fc14 |
completed | June 29, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.