Triple
T32130200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birdie Leigh Silverstein |
E820620
|
entity |
| Predicate | publiclyMentionedBy |
P197708
|
FINISHED |
| Object | Busy Philipps |
—
|
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: Busy Philipps | Statement: [Birdie Leigh Silverstein, publiclyMentionedBy, Busy Philipps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publiclyMentionedBy Context triple: [Birdie Leigh Silverstein, publiclyMentionedBy, Busy Philipps]
-
A.
mentionedWith
Indicates that two entities are mentioned together or in close association within the same context, such as a document, sentence, or conversation.
-
B.
eraMentioned
Indicates that a specific historical or temporal era is explicitly referenced or mentioned in a given context.
-
C.
mentionedAs
Indicates that one entity is referred to or cited by name or description in the context of another entity.
-
D.
mentionedVia
Indicates that one entity is referenced or brought up through a particular medium, channel, or mechanism represented by another entity.
-
E.
subsequentMentions
Indicates that one entity is mentioned again after a prior mention of the same or related entity in a discourse or text.
- 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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fea2d0a4d08190aa06aeb902a02d5a |
completed | May 9, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69fea24698348190b9b992a8e7cdbcd0 |
completed | May 9, 2026, 2:56 a.m. |
| PDg | Predicate description generation | batch_69fea2cfcd648190a15e5b90889095b1 |
completed | May 9, 2026, 2:58 a.m. |
Created at: May 1, 2026, 12:29 a.m.