Triple
T35308904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tenenbaum |
E1019710
|
entity |
| Predicate | notableCharacterBearingName |
—
|
GENERATED |
| Object | Royal Tenenbaum |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCharacterBearingName Context triple: [Tenenbaum, notableCharacterBearingName, Royal Tenenbaum]
-
A.
notableCharacterName
chosen
Indicates that the subject has a notable or significant character whose name is given by the object.
-
B.
notableAsNamesakeOf
Indicates that one entity is recognized or distinguished specifically for being the namesake of another entity.
-
C.
notableCharacterType
Indicates that an entity is a notable or prominent example of a specified character type or role.
-
D.
namedForNotablePersonFrom
Indicates that one entity is named in honor of a notable person who originates from another specified place or group.
-
E.
hasNamesakeNotability
Indicates that one entity is notable or recognized specifically because it shares the same name as another entity.
- F. None of above.
Provenance (1 batch)
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_69f76de8b4c48190ae504b86185c474c |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:03 p.m.