Triple
T28802698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeanne Samary |
E727283
|
entity |
| Predicate | notableAsModelIn |
P103614
|
FINISHED |
| Object | Portrait of Jeanne Samary |
—
|
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: Portrait of Jeanne Samary | Statement: [Jeanne Samary, notableAsModelIn, Portrait of Jeanne Samary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAsModelIn Context triple: [Jeanne Samary, notableAsModelIn, Portrait of Jeanne Samary]
-
A.
notableModel
Indicates that an entity is a particularly important, influential, or exemplary instance or version within a broader category or system.
-
B.
notableModelDeveloped
Indicates that an entity is recognized for having created, designed, or developed a significant or noteworthy model.
-
C.
notableModelingWork
chosen
Indicates that an entity is recognized for significant or prominent work in the field of modeling.
-
D.
notableModelClass
Indicates that an entity is a notable or representative instance of a particular model class.
-
E.
notableModelFamily
Indicates that one entity is a prominent or widely recognized model family associated with, produced by, or otherwise notably linked to 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_69f0319b7c44819085736bcc256185e6 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_6a018f9c7cf88190adc5daf3806f2077 |
completed | May 11, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_6a018ca4e0e481908091f0c1f8a4c31b |
completed | May 11, 2026, 8 a.m. |
Created at: April 28, 2026, 6:27 a.m.