Triple
T18395852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dahlia |
E449866
|
entity |
| Predicate | productionHistoryOfWork |
P105024
|
FINISHED |
| Object | long-gestating collaboration |
—
|
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: long-gestating collaboration | Statement: [Dahlia, productionHistoryOfWork, long-gestating collaboration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productionHistoryOfWork Context triple: [Dahlia, productionHistoryOfWork, long-gestating collaboration]
-
A.
hasProductionHistory
chosen
Indicates that an entity is associated with a record or account of its past production activities, processes, or outputs.
-
B.
historicProduct
Indicates that a product is no longer current and is recognized as belonging to an earlier or past period in the product’s lifecycle.
-
C.
productionBy
Indicates that something is created, manufactured, or generated by a particular agent, organization, or process.
-
D.
previousWorkByProducer
Indicates that a work was created earlier by the same producer responsible for another referenced work.
-
E.
producerOfWork
Indicates that one entity is the creator or originator responsible for producing a particular work.
- 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_69d8b9fab8a8819086a9ddc0871715e0 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e51846bb4c8190990f42a792a78ee0 |
completed | April 19, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69e44ff1f92c8190afbb8e85d12bf2a9 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:46 a.m.