Triple
T33497396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaminker |
E857899
|
entity |
| Predicate | isPartOfPersonalNameHistoryOf |
P175129
|
FINISHED |
| Object | Simone Signoret |
—
|
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: Simone Signoret | Statement: [Kaminker, isPartOfPersonalNameHistoryOf, Simone Signoret]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfPersonalNameHistoryOf Context triple: [Kaminker, isPartOfPersonalNameHistoryOf, Simone Signoret]
-
A.
historicalNameGivenBy
Indicates that one entity is the name historically assigned to another entity by a specific source, culture, or period.
-
B.
historicalNameUntil
Indicates that an entity bore a particular historical name up to a specified point in time, after which that name was no longer used.
-
C.
isHistoricalName
chosen
Indicates that a given name is a former or past designation historically used for an entity.
-
D.
eraNameUsedInHistoriography
Indicates that a particular historical era name is used within historiographical writing or scholarship to refer to a period or context.
-
E.
historicalNameType
Indicates that the relationship specifies the type or category of a historical name associated with an 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_69f3497660508190a541826a81f7e9ab |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff1ba8694481909ceb36f26ca85612 |
completed | May 9, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69ff1b27f0f08190a9e74308c5b3d1ba |
completed | May 9, 2026, 11:31 a.m. |
Created at: May 1, 2026, 1:38 a.m.