Triple
T2492605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Debbie Millman |
E52078
|
entity |
| Predicate | hasInterviewed |
P3970
|
FINISHED |
| Object | designers |
—
|
LITERAL 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: designers | Statement: [Debbie Millman, hasInterviewed, designers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInterviewed Context triple: [Debbie Millman, hasInterviewed, designers]
-
A.
hasGivenNumberOfInterviewsAbout
Indicates that an entity has conducted or participated in a specified number of interviews concerning another entity or topic.
-
B.
hasSpokenAbout
Indicates that one entity has verbally expressed, discussed, or mentioned another entity or topic.
-
C.
hasLiveSpokenIntroductions
Indicates that one entity provides live, spoken introductory remarks or presentations for another entity or event.
-
D.
hasInteraction
chosen
Indicates that there is some form of interaction or mutual action occurring between the related entities.
-
E.
hasScreened
Indicates that one entity has shown, displayed, or evaluated another entity, typically in the context of presenting media or conducting a review or check.
- F. None of above.
Provenance (3 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_69ab4955111c8190835bf619adec21ff |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd192cad08190b13bf8e2d7149199 |
completed | March 7, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69abd0b980b481908d4932bcea4a6167 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:45 p.m.