Triple
T35277389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indigo Child |
E1018837
|
entity |
| Predicate | hasDebutStatus |
P187540
|
FINISHED |
| Object | debut release by Raury |
—
|
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: debut release by Raury | Statement: [Indigo Child, hasDebutStatus, debut release by Raury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDebutStatus Context triple: [Indigo Child, hasDebutStatus, debut release by Raury]
-
A.
hasDebutStatusForAuthor
Indicates that an author’s work or appearance is identified as their first (debut) instance in a given context.
-
B.
hasArtistDebut
Indicates that an entity marks or specifies the first public artistic appearance or debut of an artist.
-
C.
isDebutFor
chosen
Indicates that an event, work, or performance is the first public appearance or initial presentation for a particular entity.
-
D.
isDebut
Indicates that something is the first formal appearance or introduction of an entity, such as a person, work, or performance, in a particular context or domain.
-
E.
debuted
Indicates that an entity made its first public appearance, performance, or introduction at a particular time or place.
- 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_69f76de5c4788190896ad598ae7d6bc6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff45793d5c81909dc503ad1f714ee2 |
completed | May 9, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69ff41cb0e088190a6e9b03cb20e5fad |
completed | May 9, 2026, 2:16 p.m. |
Created at: May 3, 2026, 4:02 p.m.