Triple
T34104032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saul Goodman & Associates |
E874649
|
entity |
| Predicate | ownerRealNameInFiction |
P183538
|
FINISHED |
| Object | James McGill |
—
|
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: James McGill | Statement: [Saul Goodman & Associates, ownerRealNameInFiction, James McGill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownerRealNameInFiction Context triple: [Saul Goodman & Associates, ownerRealNameInFiction, James McGill]
-
A.
formerOwnerInFiction
Indicates that one entity is depicted in a fictional context as having previously owned another entity.
-
B.
authorRealNameOfCreator
Indicates that a person’s real, legal, or birth name is the true identity behind a creator who may be known by a pseudonym or handle.
-
C.
titleCharacterRealName
Indicates that a character known by a title or alias has the specified real (personal) name.
-
D.
fictionalUniverseOwner
Indicates that one entity is the creator, rights holder, or controlling owner of a particular fictional universe or setting.
-
E.
hasFamilyNameInFiction
Indicates that a fictional character is associated with a particular family name within a work of fiction.
- 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_69f349a80d4481908527317d43f5c579 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7a01efcc08190bba489a9099b8684 |
completed | May 3, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79f477c4c8190a35cb6d87b1dcbd1 |
completed | May 3, 2026, 7:17 p.m. |
Created at: May 1, 2026, 1:53 a.m.