Triple
T23962450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madame Rubinstein |
E603963
|
entity |
| Predicate | usedHonorificInBranding |
P154059
|
FINISHED |
| Object | Madame Rubinstein |
—
|
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: Madame Rubinstein | Statement: [Madame Rubinstein, usedHonorificInBranding, Madame Rubinstein]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedHonorificInBranding Context triple: [Madame Rubinstein, usedHonorificInBranding, Madame Rubinstein]
-
A.
honorificUse
Indicates that one entity refers to or addresses another using an honorific title or respectful linguistic form.
-
B.
honorificUsage
Indicates that one entity refers to or addresses another using an honorific title or respectful linguistic form.
-
C.
usedHonorificallySince
Indicates that an honorific form of address or title has been in use for referring to the entity since a specified point in time.
-
D.
hasHonorificName
Indicates that an entity is referred to by a formal or respectful title or name used as an honorific.
-
E.
hasHonorificFrom
Indicates that one entity uses or receives a particular honorific title or form of address originating from another entity or source.
- 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_69e2954222288190a7323554d0cca8d7 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d0db90c88190adc18e9ee107281b |
completed | April 29, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f167dca3608190ace9d2eef56b2af6 |
completed | April 29, 2026, 2:07 a.m. |
Created at: April 17, 2026, 9:23 p.m.