Triple
T14129526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Because of Love |
E340123
|
entity |
| Predicate | recordedFor |
P19351
|
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: [Because of Love, recordedFor, janet.]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: janet. Context triple: [Because of Love, recordedFor, 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.
Djanet
Djanet is an oasis town in southeastern Algeria, known for its prehistoric rock art, dramatic Sahara landscapes, and role as a gateway to the Tassili n'Ajjer plateau.
-
C.
Janice
Janice is a feminine given name commonly used in English-speaking countries.
-
D.
Janette
Janette is a feminine given name of English origin, often considered a diminutive or variant of Janet or Jane.
-
E.
Jana
Jana is a feminine given name commonly used in various European countries, often as a form of Johanna or Jane.
- 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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de610aa434819096671c5aabb9134a |
completed | April 14, 2026, 3:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcf7e2b0248190ba40aa8395355052 |
completed | May 7, 2026, 8:36 p.m. |
Created at: April 9, 2026, 10:23 p.m.