Triple
T36085160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | These Heaux |
E1043754
|
entity |
| Predicate | transitionedPerformerTo |
P54761
|
FINISHED |
| Object | recording artist |
—
|
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: recording artist | Statement: [These Heaux, transitionedPerformerTo, recording artist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transitionedPerformerTo Context triple: [These Heaux, transitionedPerformerTo, recording artist]
-
A.
transitionedPerformerFrom
Indicates a change in the performer responsible for an action, role, or performance from one entity to another.
-
B.
transitionedInto
Indicates that one entity changed state, form, role, or condition to become another specified state or entity.
-
C.
transitionedThrough
Indicates that an entity passed from one state, phase, or condition to another by way of an intermediate state, phase, or condition.
-
D.
laterPerformedBy
Indicates that an action or event is carried out by a particular agent at a later time than another referenced action or event.
-
E.
replacesPerformer
chosen
Indicates that one performer takes over the role, function, or position previously held by another performer.
- 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_69f76e3154908190a6f702671c2bea08 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff7595c9bc8190982c6e6e07a0c78f |
completed | May 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69ff715432a88190a25670d26614bde2 |
completed | May 9, 2026, 5:39 p.m. |
Created at: May 3, 2026, 4:08 p.m.