Triple
T10580086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Idlewild South |
E249712
|
entity |
| Predicate | previousWorkType |
P86785
|
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: [Idlewild South, previousWorkType, studio album]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousWorkType Context triple: [Idlewild South, previousWorkType, studio album]
-
A.
previousWorkInSeries
Indicates that one work directly precedes another within the same series or sequence.
-
B.
associatedWorkType
chosen
Indicates the type or category of work with which an entity is associated (e.g., publication, artwork, performance).
-
C.
previousWorkGap
Indicates a period of time during which an entity had no prior work or employment between two work-related events or positions.
-
D.
lastWork
Indicates that one entity is the most recent work (e.g., creation, project, or publication) associated with another entity.
-
E.
originallyFromWorkType
Indicates that one entity was derived, adapted, or sourced from an original work of a specified type (e.g., book, film, artwork).
- 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_69d381c9d3d48190a29ee491e1696a0e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d52759faa4819081c195488803ada9 |
completed | April 7, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69d51907b2b881908ab9a8594688ee06 |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:38 p.m.