Triple
T538157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Janet Jackson |
E12371
|
entity |
| Predicate | notableWork |
P4
|
FINISHED |
| Object | Janet. |
E74976
|
NE 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: Janet. | Statement: [Janet Jackson, notableWork, Janet.]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Janet. Context triple: [Janet Jackson, notableWork, Janet.]
-
A.
Janet
chosen
Janet is a feminine given name commonly used in English-speaking countries, often associated with notable figures in entertainment and public life.
-
B.
Janice
Janice is a feminine given name commonly used in English-speaking countries.
-
C.
Nancy
Nancy is a feminine given name of Hebrew origin meaning "grace" that became especially popular in English-speaking countries in the 20th century.
-
D.
Jennifer
Jennifer is a common feminine given name of English origin, derived from the Cornish form of Guinevere and widely used in many English-speaking countries.
-
E.
Jane
Jane is a feminine given name of English origin that has been widely used in many English-speaking countries for centuries.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a496dc0aac8190afb75ec6c47a1d2d |
completed | March 1, 2026, 7:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a5216a74088190bf8d363d32952c28 |
completed | March 2, 2026, 5:34 a.m. |
Created at: March 1, 2026, 7:32 p.m.