Triple
T9424347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hits (Joni Mitchell album) |
E227231
|
entity |
| Predicate | previousTitleType |
P6489
|
FINISHED |
| Object | studio album |
—
|
LITERAL 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: studio album | Statement: [Hits (Joni Mitchell album), previousTitleType, studio album]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousTitleType Context triple: [Hits (Joni Mitchell album), previousTitleType, studio album]
-
A.
previousTitle
Indicates that one title held or used by an entity directly preceded another title in sequence or time.
-
B.
predecessorTitleContext
Indicates that the relationship specifies the contextual circumstances (such as role, period, or setting) under which a predecessor’s title is relevant or applies.
-
C.
predecessorTitleHolder
Indicates that one entity previously held a particular title or position before another entity.
-
D.
titleType
chosen
Indicates the specific category or kind of title associated with an entity (e.g., whether it is a main title, alternative title, working title, etc.).
-
E.
traditionalTitleGivenBy
Indicates that one entity has conferred or assigned a traditional or customary title 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_69ca8436ba308190903e470776d2d893 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd6c29b4348190b45103e9ebd82aa4 |
completed | April 1, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69cca550777c819094e1851a6127cbbc |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:49 p.m.