Triple
T28275524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bruce Weber |
E712976
|
entity |
| Predicate | hasWorkedWithPublication |
P94242
|
FINISHED |
| Object | Vogue |
—
|
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: Vogue | Statement: [Bruce Weber, hasWorkedWithPublication, Vogue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkedWithPublication Context triple: [Bruce Weber, hasWorkedWithPublication, Vogue]
-
A.
workedForPublication
chosen
Indicates that an entity was employed by or contributed work to a particular publication (such as a newspaper, magazine, or journal).
-
B.
hasRelatedPublication
Indicates that an entity is associated with one or more publications that are relevant or connected to it in content, context, or subject matter.
-
C.
hasPublication
Indicates that an entity is associated with or responsible for a specific publication.
-
D.
hasPrintPublications
Indicates that an entity possesses or is associated with one or more printed publications (such as books, journals, or other print media).
-
E.
hasEditorialWork
Indicates that one entity performs, contributes to, or is responsible for editorial work on another entity.
- 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_69efb52275788190ae5181ccebef18ce |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 27, 2026, 11:20 p.m.