Triple
T38107054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lilli Cooper |
E951542
|
entity |
| Predicate | hasGivenPerformanceAt |
P190020
|
FINISHED |
| Object | Broadway |
—
|
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: Broadway | Statement: [Lilli Cooper, hasGivenPerformanceAt, Broadway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGivenPerformanceAt Context triple: [Lilli Cooper, hasGivenPerformanceAt, Broadway]
-
A.
hasNotablePerformanceIn
Indicates that an entity delivered a significant or distinguished performance within a specified work, event, or context.
-
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.
performedTo
Indicates that an action or performance is directed toward or carried out on a particular entity.
-
D.
hasDJPerformances
Indicates that an entity features or hosts performances by a DJ.
-
E.
hasLivePerformanceWith
Indicates that two or more entities participate together in the same live performance event.
- 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_69f76f065ed08190bdfb1b6d817f5b39 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69fc4747b06c8190a3ea5331f02eedad |
completed | May 7, 2026, 8:03 a.m. |
Created at: May 3, 2026, 4:21 p.m.