Triple
T20398325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gentlemen Marry Brunettes |
E500264
|
entity |
| Predicate | followUpDescription |
P139983
|
FINISHED |
| Object | serves as a follow-up to Gentlemen Prefer Blondes |
—
|
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: serves as a follow-up to Gentlemen Prefer Blondes | Statement: [Gentlemen Marry Brunettes, followUpDescription, serves as a follow-up to Gentlemen Prefer Blondes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followUpDescription Context triple: [Gentlemen Marry Brunettes, followUpDescription, serves as a follow-up to Gentlemen Prefer Blondes]
-
A.
followUpType
Indicates the specific category or nature of a follow-up action or interaction that occurs after an initial event or communication.
-
B.
followsUp
Indicates that one entity continues, responds to, or builds upon a previous entity, typically as a subsequent action, communication, or step.
-
C.
followUpMechanism
Indicates a mechanism or process that is used to continue, monitor, or respond to a prior action, event, or communication.
-
D.
followUpRelease
Indicates that one release occurs subsequently as a continuation or update to a previous release.
-
E.
endingDescribedBy
Indicates that the conclusion or final part of something is characterized, explained, or detailed by a particular description or representation.
- 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_69e0b4a81bec8190b69adfdc1336a015 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6798c2b28819092fab93f01218cde |
completed | April 20, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:29 a.m.