Triple
T14006961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ready to Love |
E336973
|
entity |
| Predicate | hasCastingCriteria |
P50251
|
FINISHED |
| Object | professionally successful singles |
—
|
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: professionally successful singles | Statement: [Ready to Love, hasCastingCriteria, professionally successful singles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCastingCriteria Context triple: [Ready to Love, hasCastingCriteria, professionally successful singles]
-
A.
hasCasting
Indicates that an entity features a particular actor or set of actors in its cast.
-
B.
hasQualityCriterion
chosen
Indicates that something is associated with a specific standard or criterion used to judge its quality.
-
C.
hasMinimalCast
Indicates that an entity (such as a film or production) involves only a small or minimal number of cast members.
-
D.
hasMultipleCasts
Indicates that an entity is associated with more than one distinct cast or casting instance.
-
E.
hasCast
Indicates that a creative work features a particular group of performers or actors.
- 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_69d81c645c5c8190b1fd16a285a1b78a |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2ed327d88190a53af5768468a8eb |
completed | April 14, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69dd465dfbc4819090d8c61fd572d35f |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:19 p.m.