Triple
T37055972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Queen and I |
E917185
|
entity |
| Predicate | hasAssociatedLabelGroup |
P44780
|
FINISHED |
| Object | Fueled by Ramen / Decaydance scene |
—
|
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: Fueled by Ramen / Decaydance scene | Statement: [The Queen and I, hasAssociatedLabelGroup, Fueled by Ramen / Decaydance scene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedLabelGroup Context triple: [The Queen and I, hasAssociatedLabelGroup, Fueled by Ramen / Decaydance scene]
-
A.
hasRelatedGroup
Indicates that one group or collection is associated with another group or collection through some defined relationship or connection.
-
B.
hasLabelSet
chosen
Indicates that an entity is associated with a specific collection or set of labels.
-
C.
hasLabel
Indicates that an entity is associated with a specific textual label or name used to identify or describe it.
-
D.
associatedWithLabel
Indicates that an entity is connected or related to a particular label or tag used to categorize or identify it.
-
E.
associatedWithLabelFamily
Indicates that one entity is connected to or grouped with another through a shared label family or labeling category.
- 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_69f76e94d0308190a3f06890e133c88e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
Created at: May 3, 2026, 4:14 p.m.