Triple
T29428391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daisy Diamond |
E746357
|
entity |
| Predicate | hasLeadPerformanceBy |
P184375
|
FINISHED |
| Object | Noomi Rapace |
—
|
NE NERFINISHED |
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: Noomi Rapace | Statement: [Daisy Diamond, hasLeadPerformanceBy, Noomi Rapace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeadPerformanceBy Context triple: [Daisy Diamond, hasLeadPerformanceBy, Noomi Rapace]
-
A.
leadPerformanceType
Indicates the specific kind of performance in which an entity takes a leading role.
-
B.
hasAwardedPerformanceBy
Indicates that an award or recognition has been given to a performance by a specific entity (such as a person or organization).
-
C.
leadPerformanceDescribedAs
Indicates that a lead performance is characterized or labeled using a particular description or qualitative assessment.
-
D.
hasNotablePerformanceIn
Indicates that an entity delivered a significant or distinguished performance within a specified work, event, or context.
-
E.
forPerformanceBy
Indicates that something is intended, designed, or suitable to be performed by a particular agent or performer.
- F. None of above. chosen
Provenance (4 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_69f0a7a06e0081908add494075912eb4 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69f7b0e3917481908a394680d76743c3 |
completed | May 3, 2026, 8:32 p.m. |
Created at: April 28, 2026, 3:11 p.m.